Triple
T21279603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTRAN |
E524482
|
entity |
| Predicate | IubInterfaceConnects |
P64333
|
FINISHED |
| Object | RNC to Node B |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: RNC to Node B | Statement: [UTRAN, IubInterfaceConnects, RNC to Node B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IubInterfaceConnects Context triple: [UTRAN, IubInterfaceConnects, RNC to Node B]
-
A.
L2Is
Indicates that one entity is located at or occupies a specific level 2 (L2) position or layer relative to another entity.
-
B.
interconnectionType
chosen
Indicates the specific kind or nature of relationship that links two or more entities together.
-
C.
interconnectionFrequency
Indicates how often two or more entities are connected or interact with each other over a given period.
-
D.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or system.
-
E.
supportsInterconnection
Indicates that one entity enables, facilitates, or maintains a connection or interoperability between two or more other entities.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73659b56c8190af283348378b1cff |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.