Triple
T27795827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Mi Teleférico) |
E701205
|
entity |
| Predicate | systemBranding |
P11989
|
FINISHED |
| Object | Mi Teleférico color line |
—
|
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: Mi Teleférico color line | Statement: [Green Line (Mi Teleférico), systemBranding, Mi Teleférico color line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemBranding Context triple: [Green Line (Mi Teleférico), systemBranding, Mi Teleférico color line]
-
A.
systemBrand
Indicates the brand or manufacturer associated with a particular system.
-
B.
hasBranding
chosen
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
C.
brandingReplaced
Indicates that one branding has been superseded or substituted by another branding.
-
D.
sharesBrandingWith
Indicates that two entities use the same or closely related branding elements, such as name, logo, or visual identity.
-
E.
marketingIdentity
Indicates a relationship where one entity serves as the brand, persona, or public-facing identity used to market or promote another entity.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 5:31 p.m.