Triple
T16295507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Line (Los Angeles Metro) |
E395635
|
entity |
| Predicate | formerDesignationPeriod |
P78284
|
FINISHED |
| Object | 1990–2019 |
—
|
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: 1990–2019 | Statement: [A Line (Los Angeles Metro), formerDesignationPeriod, 1990–2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDesignationPeriod Context triple: [A Line (Los Angeles Metro), formerDesignationPeriod, 1990–2019]
-
A.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
C.
formerNamePeriodEnd
Indicates the point in time when an entity stopped using a former name.
-
D.
officialNameDuringPeriod
Indicates that an entity had a specific official name that was valid only during a particular time period.
-
E.
previousNamePeriod
chosen
Indicates the time span during which an entity was known by a former name before changing to its current name.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2d08108190bab1b3325923af1d |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.