Triple
T3277542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannibal, Missouri |
E68792
|
entity |
| Predicate | stateHighwayServedBy |
P47068
|
FINISHED |
| Object | U.S. Route 61 |
—
|
NE NERFINISHED |
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: U.S. Route 61 | Statement: [Hannibal, Missouri, stateHighwayServedBy, U.S. Route 61]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayServedBy Context triple: [Hannibal, Missouri, stateHighwayServedBy, U.S. Route 61]
-
A.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
B.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
-
C.
servedByFreeway
Indicates that a location or area is directly accessed or connected by a freeway.
-
D.
isPrimaryStateHighway
Indicates that a given road segment is designated as a primary (major) state highway within a state’s road network.
-
E.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb013de048190bcaac732caa6b174 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.