Triple
T33605342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulse Dempster Line |
E860833
|
entity |
| Predicate | hasPriorityFeatures |
P182
|
FINISHED |
| Object | bus rapid transit features |
—
|
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 rapid transit features | Statement: [Pulse Dempster Line, hasPriorityFeatures, bus rapid transit features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriorityFeatures Context triple: [Pulse Dempster Line, hasPriorityFeatures, bus rapid transit features]
-
A.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
E.
hasSideFeature
Indicates that an entity possesses a specific secondary or auxiliary feature on its side or lateral aspect.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01ade363088190b3a3e3dedabd1aa2 |
completed | May 11, 2026, 10:22 a.m. |
| PD | Predicate disambiguation | batch_6a01acf3c5788190932bd8fcf27c123d |
completed | May 11, 2026, 10:18 a.m. |
Created at: May 1, 2026, 1:41 a.m.