Triple
T26779795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTD light rail |
E670215
|
entity |
| Predicate | expansionProgram |
P50445
|
FINISHED |
| Object | FasTracks |
—
|
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: FasTracks | Statement: [RTD light rail, expansionProgram, FasTracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionProgram Context triple: [RTD light rail, expansionProgram, FasTracks]
-
A.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
B.
expansionProject
chosen
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
C.
extendsProgramsOf
Indicates that one program builds upon, enhances, or broadens the scope of another program’s content, features, or capabilities.
-
D.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
E.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:08 a.m.