Triple
T36433558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anselm |
E897507
|
entity |
| Predicate | hasLocationOfDeath |
P21
|
FINISHED |
| Object | Roncevaux Pass |
—
|
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: Roncevaux Pass | Statement: [Anselm, hasLocationOfDeath, Roncevaux Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationOfDeath Context triple: [Anselm, hasLocationOfDeath, Roncevaux Pass]
-
A.
placeOfDeath
chosen
Indicates the location where an entity (typically a person or animal) died.
-
B.
presentDayLocationOfDeath
Indicates the current-day geographic location where an entity’s death occurred, expressed in terms of modern political or administrative boundaries.
-
C.
fatalitiesLocation
Indicates the place where deaths or fatal incidents occurred.
-
D.
deathOccurred
Indicates that a death event has taken place involving the specified entity or entities.
-
E.
traditionalPlaceOfDeath
Indicates the location where a person is customarily or culturally considered to have died, according to traditional or historical accounts.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 4:10 p.m.