Triple
T21662912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Paravane |
E534636
|
entity |
| Predicate | statusOfTargetAfterOperation |
P103440
|
FINISHED |
| Object | Tirpitz still afloat |
—
|
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: Tirpitz still afloat | Statement: [Operation Paravane, statusOfTargetAfterOperation, Tirpitz still afloat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfTargetAfterOperation Context triple: [Operation Paravane, statusOfTargetAfterOperation, Tirpitz still afloat]
-
A.
operationalStatusAtEnd
Indicates the final operational condition or state of an entity at the conclusion of a specified period or process.
-
B.
statusAfterRelocation
Indicates the condition or state an entity has once it has been moved from its original location to a new one.
-
C.
statusAfterMission
chosen
Indicates the condition or state an entity is in following the completion of a mission.
-
D.
targetOSStatus
Indicates the operational or lifecycle state currently associated with the specified target operating system.
-
E.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0956e0819093b4794418efe052 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.