Triple
T27646008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOCs |
E696713
|
entity |
| Predicate | provideInterconnectionTo |
P115265
|
FINISHED |
| Object | interexchange carriers |
—
|
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: interexchange carriers | Statement: [BOCs, provideInterconnectionTo, interexchange carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provideInterconnectionTo Context triple: [BOCs, provideInterconnectionTo, interexchange carriers]
-
A.
supportsInterconnection
chosen
Indicates that one entity enables, facilitates, or maintains a connection or interoperability between two or more other entities.
-
B.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
C.
hasMajorInterconnection
Indicates that there exists a significant, primary, or high-capacity connection or linkage between two entities.
-
D.
hasIXP
Indicates that an entity is connected to or participates in a specific Internet Exchange Point (IXP).
-
E.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 2:29 p.m.