Triple
T16680254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 119 |
E405319
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | AL 119 |
E843133
|
NE 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: AL 119 | Statement: [Alabama State Route 119, abbreviation, AL 119]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AL 119 Context triple: [Alabama State Route 119, abbreviation, AL 119]
-
A.
AL 119
chosen
AL 119 is a state highway in Alabama that serves as a regional connector route through several central Alabama communities.
-
B.
AL 139
AL 139 is a state highway in Alabama that serves as a regional connector route between local communities.
-
C.
AL 155
AL 155 is a state highway in Alabama that serves as a connector route within the state's road network.
-
D.
AL 14
AL 14 is a state highway in Alabama that runs east–west across the central part of the state, connecting several communities and major routes.
-
E.
AL 21
AL 21 is a primary state highway in Alabama that runs north–south across the state, connecting several major towns and highways.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6e74ec81909ea95c3e4b0113ab |
completed | April 18, 2026, 12:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a3e2ddc8190a59108cdf001dac2 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 10, 2026, 5:19 a.m.