Triple
T2039958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-505 |
E44718
|
entity |
| Predicate | decommissionedAsWarship |
P10134
|
FINISHED |
| Object | post-World War II |
—
|
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: post-World War II | Statement: [U-505, decommissionedAsWarship, post-World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedAsWarship Context triple: [U-505, decommissionedAsWarship, post-World War II]
-
A.
strickenFromNavalRegister
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
-
B.
decommissionedReason
chosen
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
C.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
D.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.