Triple
T8506179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 26 |
E201337
|
entity |
| Predicate | signedDirectionInSouthCarolina |
P44650
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Interstate 26, signedDirectionInSouthCarolina, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedDirectionInSouthCarolina Context triple: [Interstate 26, signedDirectionInSouthCarolina, east–west]
-
A.
geographicDirectionWithinState
chosen
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
B.
directionFromSavannah
Indicates the cardinal or relative compass direction in which one entity is located from Savannah.
-
C.
isInUnitedStatesSouth
Indicates that something is located within the southern region of the United States.
-
D.
borderDirectionFromKentucky
Indicates the compass direction in which another region lies relative to Kentucky along their shared border.
-
E.
directionInSouthernHemisphere
Indicates that the specified direction is defined or measured relative to locations or reference frames in the Southern Hemisphere.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5db51e4819098dde316e87e8b0d |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.