Triple
T29716562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Red Line (Los Angeles) |
E751923
|
entity |
| Predicate | lineDesignationReplacedBy |
P17520
|
FINISHED |
| Object | B Line |
—
|
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: B Line | Statement: [Metro Red Line (Los Angeles), lineDesignationReplacedBy, B Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineDesignationReplacedBy Context triple: [Metro Red Line (Los Angeles), lineDesignationReplacedBy, B Line]
-
A.
lineDesignationIntroducedBy
Indicates that a particular line designation was introduced or established by a specific agent or source.
-
B.
replacedInNewDesignsBy
Indicates that an element or component is superseded and functionally taken over by another element or component in newer designs.
-
C.
UScodeDesignationReplacedBy
Indicates that one U.S. legal code designation has been superseded and replaced by another designation.
-
D.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
E.
formerLineName
chosen
Indicates that the object is a previous or former name by which the referenced line was known.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672dd9ab881908969657a9bd48098 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:34 p.m.