Triple
T33633484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Officer Commanding XIII Corps |
E861628
|
entity |
| Predicate | positionHolderDeathYear |
P16526
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [General Officer Commanding XIII Corps, positionHolderDeathYear, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHolderDeathYear Context triple: [General Officer Commanding XIII Corps, positionHolderDeathYear, 1942]
-
A.
yearOfDeath
chosen
Indicates the specific year in which an entity (typically a person or organism) died.
-
B.
compilerDeathYearGregorian
Indicates the year, in the Gregorian calendar, in which the compiler of a work died.
-
C.
deathYearInvestigated
Indicates that an entity’s year of death has been the subject of investigation or inquiry.
-
D.
deathYearApproximate
Indicates that the year of an entity’s death is known only approximately rather than as an exact calendar year.
-
E.
deathYearInferredFrom
Indicates that an entity’s year of death is not directly known but has been deduced based on other available information or evidence.
- 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_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:41 a.m.