Triple
T21279602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTRAN |
E524482
|
entity |
| Predicate | IuInterfaceConnects |
P845
|
FINISHED |
| Object | UTRAN to Core Network |
—
|
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: UTRAN to Core Network | Statement: [UTRAN, IuInterfaceConnects, UTRAN to Core Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IuInterfaceConnects Context triple: [UTRAN, IuInterfaceConnects, UTRAN to Core Network]
-
A.
relatedInterface
Indicates that one interface is associated or connected to another interface in a relevant or dependent way.
-
B.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
designedToInterfaceWith
Indicates that one entity has been intentionally created or configured to connect, interact, or work compatibly with another entity.
-
D.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
E.
connectsSystem
Indicates that one system establishes a link or interface with another system, enabling interaction or data exchange between them.
- 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.