Triple
T30292157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Liner |
E770407
|
entity |
| Predicate | replacedByBrand |
P157594
|
FINISHED |
| Object | Metro Busway system |
—
|
NE NERFINISHED |
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: Metro Busway system | Statement: [Metro Liner, replacedByBrand, Metro Busway system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByBrand Context triple: [Metro Liner, replacedByBrand, Metro Busway system]
-
A.
brandingReplaced
chosen
Indicates that one branding has been superseded or substituted by another branding.
-
B.
laterBrandOf
Indicates that one brand is a subsequent or successor brand to another, coming into use at a later time.
-
C.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
D.
replacedInNewDesignsBy
Indicates that an element or component is superseded and functionally taken over by another element or component in newer designs.
-
E.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 7:47 p.m.