Triple
T16984895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 46 |
E412037
|
entity |
| Predicate | formerDesignationPart |
P116490
|
FINISHED |
| Object | U.S. Route 466 |
—
|
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 466 | Statement: [California State Route 46, formerDesignationPart, U.S. Route 466]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDesignationPart Context triple: [California State Route 46, formerDesignationPart, U.S. Route 466]
-
A.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
formerPart
chosen
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
C.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
-
D.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
E.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18a0bf881908c449f499eb86495 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.