Triple
T616049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral Graf Spee |
E14405
|
entity |
| Predicate | reasonForScuttling |
P17168
|
FINISHED |
| Object | to avoid internment and capture |
—
|
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: to avoid internment and capture | Statement: [Admiral Graf Spee, reasonForScuttling, to avoid internment and capture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForScuttling Context triple: [Admiral Graf Spee, reasonForScuttling, to avoid internment and capture]
-
A.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
B.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
C.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
-
D.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
E.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
- F. None of above. chosen
Provenance (4 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.