Triple
T1691981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 21 |
E36569
|
entity |
| Predicate | northernTerminusLocation |
P3375
|
FINISHED |
| Object | northeastern Alabama |
—
|
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: northeastern Alabama | Statement: [Alabama State Route 21, northernTerminusLocation, northeastern Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTerminusLocation Context triple: [Alabama State Route 21, northernTerminusLocation, northeastern Alabama]
-
A.
locatedAtNorthernEndOf
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
-
B.
northernTerminusState
Indicates that a location or route has its northern endpoint or terminus within the specified state.
-
C.
terminusNorth
chosen
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
D.
northernmostNeighborhoodOf
Indicates that one neighborhood is located farther north than any other neighborhood within the specified area or jurisdiction.
-
E.
locatedNorthOf
Indicates that one entity is positioned geographically 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_69a886151508819084fa7f1ce6e05577 |
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_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.