Triple
T17691347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandie dry dock |
E441033
|
entity |
| Predicate | statusAfterRaid |
P90752
|
FINISHED |
| Object | put out of action for the remainder of 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: put out of action for the remainder of World War II | Statement: [Normandie dry dock, statusAfterRaid, put out of action for the remainder of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterRaid Context triple: [Normandie dry dock, statusAfterRaid, put out of action for the remainder of World War II]
-
A.
statusAfterAttack
chosen
Indicates the resulting condition or state of an entity after an attack has occurred.
-
B.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
-
C.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
D.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
E.
statusAfterSmaug
Indicates the resulting status or condition of an entity after an event or interaction involving Smaug has occurred.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47152306c819086d483d87348db5d |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.