Triple
T4481737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistema de Transporte Colectivo |
E100149
|
entity |
| Predicate | hasOfficialTwitterAccount |
P2866
|
FINISHED |
| Object | https://twitter.com/MetroCDMX |
—
|
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: https://twitter.com/MetroCDMX | Statement: [Sistema de Transporte Colectivo, hasOfficialTwitterAccount, https://twitter.com/MetroCDMX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialTwitterAccount Context triple: [Sistema de Transporte Colectivo, hasOfficialTwitterAccount, https://twitter.com/MetroCDMX]
-
A.
hasOfficialInstagram
Indicates that an entity possesses or is associated with an official Instagram account.
-
B.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
C.
twitterHandle
chosen
Indicates that one entity is the Twitter username or account identifier associated with another entity.
-
D.
twitterUsername
Indicates that one entity is the Twitter handle or username associated with another entity.
-
E.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:36 p.m.