Triple
T1655625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DART St. Paul Station |
E35791
|
entity |
| Predicate | zoneSystem |
P2160
|
FINISHED |
| Object | DART local and regional zones |
—
|
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: DART local and regional zones | Statement: [DART St. Paul Station, zoneSystem, DART local and regional zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneSystem Context triple: [DART St. Paul Station, zoneSystem, DART local and regional zones]
-
A.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
B.
timeZoneType
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
-
C.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
D.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
E.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.