Triple
T18370751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorta |
E446173
|
entity |
| Predicate | deathPractice |
P130861
|
FINISHED |
| Object | often commit suicide to avoid capture |
—
|
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: often commit suicide to avoid capture | Statement: [Vorta, deathPractice, often commit suicide to avoid capture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathPractice Context triple: [Vorta, deathPractice, often commit suicide to avoid capture]
-
A.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
D.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
E.
deathIs
Indicates that one entity is the cause, manner, or circumstance of another entity’s 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5175324e48190a00572e15423feb7 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:44 a.m.