Triple
T38449933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa 965 |
E912144
|
entity |
| Predicate | formerHighwayDesignation |
P135070
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Iowa 965, formerHighwayDesignation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerHighwayDesignation Context triple: [Iowa 965, formerHighwayDesignation, yes]
-
A.
formerConstituentHighway
chosen
Indicates that a highway was once part of, but is no longer included in, another highway or highway system.
-
B.
stateHighwayNumberingReplacedBy
Indicates that an existing state highway’s numbering system has been superseded and replaced by a new numbering designation.
-
C.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
D.
highwayNumberingStatus
Indicates the current designation or classification state of a highway within an official numbering system.
-
E.
highwayNumberingSystem
Indicates a system that assigns and organizes numerical designations to highways within a road network.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: May 3, 2026, 4:31 p.m.