Triple
T16301666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 91 |
E395803
|
entity |
| Predicate | mayBeDecommissionedBy |
P115383
|
FINISHED |
| Object | state transportation authorities |
—
|
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: state transportation authorities | Statement: [SR 91, mayBeDecommissionedBy, state transportation authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDecommissionedBy Context triple: [SR 91, mayBeDecommissionedBy, state transportation authorities]
-
A.
decommissionedBy
chosen
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
B.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
C.
estimatedDecommissioningDuration
Indicates the expected length of time required to complete the decommissioning process of an entity.
-
D.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
E.
isDecommissionedRoute
Indicates that a route has been officially taken out of service and is no longer in active use.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e32da7081908d8bd320374a5731 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.