Triple
T18933765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan Sánchez-Villalobos Ramírez |
E463184
|
entity |
| Predicate | deathStyle |
P11798
|
FINISHED |
| Object | beheaded by the Kurgan (in Highlander film continuity) |
—
|
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: beheaded by the Kurgan (in Highlander film continuity) | Statement: [Juan Sánchez-Villalobos Ramírez, deathStyle, beheaded by the Kurgan (in Highlander film continuity)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathStyle Context triple: [Juan Sánchez-Villalobos Ramírez, deathStyle, beheaded by the Kurgan (in Highlander film continuity)]
-
A.
deathMethod
chosen
Indicates the specific way or means by which a death occurred.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathRite
Indicates a ritual, ceremony, or set of practices performed in connection with someone's death or burial.
-
D.
deathPractice
Indicates a relationship where an entity engages in practices, rituals, or preparations specifically related to death or dying.
-
E.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e57e648190aa4d3b09e84d4d38 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.