Triple
T31737219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo Line (Los Angeles Metro) |
E810033
|
entity |
| Predicate | phase1Opening |
P51679
|
FINISHED |
| Object | April 28, 2012 |
—
|
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: April 28, 2012 | Statement: [Expo Line (Los Angeles Metro), phase1Opening, April 28, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phase1Opening Context triple: [Expo Line (Los Angeles Metro), phase1Opening, April 28, 2012]
-
A.
phasedOpening
Indicates that the opening or launch of something occurs in multiple planned stages or phases rather than all at once.
-
B.
phase1OpeningDate
chosen
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
C.
phase1Section
Indicates that something belongs to, occurs within, or is associated with the first phase or section of a larger process or structure.
-
D.
phase1Purpose
Indicates that one entity serves as the specific purpose, goal, or intended outcome of the first phase of another entity, process, or project.
-
E.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab24dc708190b7df11a2b968847d |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:23 p.m.