Triple
T4171555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte LYNX Blue Line |
E84574
|
entity |
| Predicate | expansionOpeningYear |
P12553
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Charlotte LYNX Blue Line, expansionOpeningYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionOpeningYear Context triple: [Charlotte LYNX Blue Line, expansionOpeningYear, 2018]
-
A.
expansionOpeningDate
chosen
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
B.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
expansionAnnouncementYear
Indicates the year in which an expansion (such as a project, product, or service extension) was officially announced.
-
D.
westEndOpeningYear
Indicates the calendar year in which something (typically a production or show) first opened in London’s West End.
-
E.
expansionSuccessorYear
Indicates that one year directly follows another in the sequence of years associated with an expansion.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c9e12c81908d0b22671fea2453 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.