Triple
T3574550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Missouri |
E75654
|
entity |
| Predicate | recommissionedOn |
P12197
|
FINISHED |
| Object | 1986-05-10 |
—
|
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: 1986-05-10 | Statement: [USS Missouri, recommissionedOn, 1986-05-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommissionedOn Context triple: [USS Missouri, recommissionedOn, 1986-05-10]
-
A.
recommissioned
chosen
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
-
B.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
commissionedAfter
Indicates that one entity was formally authorized, ordered, or initiated at a later time than another entity.
-
E.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
- 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.