Triple
T367819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Route 61 |
E8201
|
entity |
| Predicate | directionOrientation |
P1101
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Kentucky Route 61, directionOrientation, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOrientation Context triple: [Kentucky Route 61, directionOrientation, north–south]
-
A.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
C.
sessionOrientation
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
D.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
E.
directed
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebeab13c8190b15c2f10310ec6a8 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.