Triple
T8531495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DART downtown transit corridor |
E201960
|
entity |
| Predicate | secondaryMode |
P44999
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [DART downtown transit corridor, secondaryMode, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryMode Context triple: [DART downtown transit corridor, secondaryMode, bus]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
C.
secondaryState
Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
-
D.
secondaryMethod
chosen
Indicates that an entity serves as an additional or backup method used alongside or after a primary method in performing an action or achieving a result.
-
E.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe676e2ac8190b65a3d2a935776fd |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.