Triple
T2468912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore–Harrisburg corridor |
E55321
|
entity |
| Predicate | approximateDirection |
P40031
|
FINISHED |
| Object | south–north |
—
|
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: south–north | Statement: [Baltimore–Harrisburg corridor, approximateDirection, south–north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDirection Context triple: [Baltimore–Harrisburg corridor, approximateDirection, south–north]
-
A.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
D.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
E.
directionRelativeToARP
Indicates the spatial direction or orientation of an entity relative to a specified Aircraft Reference Point (ARP).
- F. None of above. chosen
Provenance (4 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd2baee308190bdaa41ef1f6bc9cc |
completed | March 7, 2026, 7:24 a.m. |
Created at: March 6, 2026, 9:44 p.m.