Triple
T33633486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Officer Commanding XIII Corps |
E861628
|
entity |
| Predicate | positionHolderDeathContext |
P188485
|
FINISHED |
| Object | Second World War |
—
|
NE NERFINISHED |
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: Second World War | Statement: [General Officer Commanding XIII Corps, positionHolderDeathContext, Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHolderDeathContext Context triple: [General Officer Commanding XIII Corps, positionHolderDeathContext, Second World War]
-
A.
positionOnDeath
Indicates the role, title, or position an entity held at the time of its death.
-
B.
positionOnDeathPenalty
Indicates a stance or viewpoint an entity holds regarding the use, legality, or morality of the death penalty.
-
C.
deathInContextOf
chosen
Indicates that a death occurred specifically within, or as part of, a particular situation, event, or broader contextual circumstance.
-
D.
titleHolderDeath
Indicates that the current holder of a title has died, ending their tenure in that role.
-
E.
lastHolderDiedIn
Indicates that the most recent holder or possessor of something died in the specified place or during the specified event or time period.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:41 a.m.