Triple
T9236129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Insurgentes |
E221940
|
entity |
| Predicate | partOfNetworkSince |
P87719
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Metro Insurgentes, partOfNetworkSince, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNetworkSince Context triple: [Metro Insurgentes, partOfNetworkSince, 1969]
-
A.
primaryNetworkSince
Indicates that an entity has been designated as the main or preferred network connection starting from a specific point in time.
-
B.
connectedToNationalNetworkAt
Indicates that an entity has a direct linkage or access point to a broader national-level network or infrastructure.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
isPartOfNetworkManagedBy
Indicates that an entity belongs to and operates under the control or administration of a specific network management authority or system.
-
E.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
- F. None of above. chosen
Provenance (4 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09d42488190b8ccb9c4b62fdda8 |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.