Triple
T38430712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold von Winkelried |
E903790
|
entity |
| Predicate | allegedPlaceOfDeath |
P28174
|
FINISHED |
| Object | Sempach |
—
|
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: Sempach | Statement: [Arnold von Winkelried, allegedPlaceOfDeath, Sempach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedPlaceOfDeath Context triple: [Arnold von Winkelried, allegedPlaceOfDeath, Sempach]
-
A.
placeOfDeath
Indicates the location where an entity (typically a person or animal) died.
-
B.
residenceAtDeath
Indicates the place where an individual was living at the time of their death.
-
C.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
D.
deathPlace_uncertain
chosen
Indicates that the place where an entity died is not known with certainty or is disputed.
-
E.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:31 p.m.