Triple
T19503163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Cabot |
E487952
|
entity |
| Predicate | decommissionedFromSpanishNavyOn |
P14100
|
FINISHED |
| Object | 1989-08-30 |
—
|
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: 1989-08-30 | Statement: [USS Cabot, decommissionedFromSpanishNavyOn, 1989-08-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedFromSpanishNavyOn Context triple: [USS Cabot, decommissionedFromSpanishNavyOn, 1989-08-30]
-
A.
decommissionedFromRoyalNavy
Indicates that a vessel or asset has been formally retired from active service in the Royal Navy.
-
B.
decommissionedAsWorkingVessel
Indicates that an entity has been officially retired from service and is no longer used as an active working vessel.
-
C.
strickenFromNavalRegister
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
D.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6350f8d888190a4809c83522933d4 |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.