Triple
T28386257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 80 |
E719026
|
entity |
| Predicate | decommissionedInState |
P152904
|
FINISHED |
| Object | California |
—
|
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: California | Statement: [US 80, decommissionedInState, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedInState Context triple: [US 80, decommissionedInState, California]
-
A.
placeOfDecommissioning
chosen
Indicates the location where an entity (such as a facility, vehicle, or equipment) was formally taken out of service or decommissioned.
-
B.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
C.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
D.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
E.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cbb06108190b832b66c1d96b308 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:10 a.m.