Triple
T24620664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant City station |
E609401
|
entity |
| Predicate | hasNorthboundDirection |
P102963
|
FINISHED |
| Object | toward St. George Terminal |
—
|
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: toward St. George Terminal | Statement: [Grant City station, hasNorthboundDirection, toward St. George Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthboundDirection Context triple: [Grant City station, hasNorthboundDirection, toward St. George Terminal]
-
A.
hasNorthboundPlatform
Indicates that an entity includes or is associated with a platform designated for northbound travel or service.
-
B.
hasNorthboundServicesTo
chosen
Indicates that an entity provides or supports services that travel or operate in a northbound direction to another location or entity.
-
C.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
D.
hasContinuationNorth
Indicates that something extends, continues, or has a connected part toward the north.
-
E.
hasNorthNeighbor
Indicates that one entity is located directly to the north of another 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.