Triple
T36372389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meridian Highway |
E895796
|
entity |
| Predicate | hasRouteNumberSuccessor |
P152919
|
FINISHED |
| Object | U.S. Route 81 |
—
|
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 81 | Statement: [Meridian Highway, hasRouteNumberSuccessor, U.S. Route 81]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNumberSuccessor Context triple: [Meridian Highway, hasRouteNumberSuccessor, U.S. Route 81]
-
A.
successorOnRoute
Indicates that one entity directly follows another in sequence along a specified route.
-
B.
hasRoadNumberAfter
chosen
Indicates that one road’s designated number comes later in a defined sequence or ordering than another road’s number.
-
C.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
D.
hasSuccessors
Indicates that an entity is followed or replaced by one or more subsequent entities in a sequence, process, or lineage.
-
E.
majorSuccessorRoute
Indicates that one route is the primary or main successor to another route in a sequence or network of routes.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:10 p.m.