Triple
T34503232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann von Aldringen |
E885812
|
entity |
| Predicate | presentDayLocationOfDeath |
P192448
|
FINISHED |
| Object | Germany |
—
|
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: Germany | Statement: [Johann von Aldringen, presentDayLocationOfDeath, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayLocationOfDeath Context triple: [Johann von Aldringen, presentDayLocationOfDeath, Germany]
-
A.
placeOfDeath
Indicates the location where an entity (typically a person or animal) died.
-
B.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
-
C.
placeOfCessation
Indicates the location where an entity’s existence, activity, or state comes to an end.
-
D.
residenceAtDeath
Indicates the place where an individual was living at the time of their death.
-
E.
bodyLocationAfterDeath
Indicates the location or position of an entity’s body after its death.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: May 1, 2026, 2:01 a.m.