Triple
T3574551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Missouri |
E75654
|
entity |
| Predicate | finalDecommissioningDate |
P14100
|
FINISHED |
| Object | 1992-03-31 |
—
|
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: 1992-03-31 | Statement: [USS Missouri, finalDecommissioningDate, 1992-03-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDecommissioningDate Context triple: [USS Missouri, finalDecommissioningDate, 1992-03-31]
-
A.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
B.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
C.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
D.
estimatedDecommissioningDuration
Indicates the expected length of time required to complete the decommissioning process of an entity.
-
E.
divestitureDate
Indicates the date on which an entity formally disposes of, sells, or otherwise relinquishes ownership or control of an asset, business unit, or investment.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0d928f08190830347b3b032178a |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.