Triple
T6978588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pythonidae |
E161778
|
entity |
| Predicate | hasConstrictionAsKillingMethod |
P57707
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pythonidae, hasConstrictionAsKillingMethod, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstrictionAsKillingMethod Context triple: [Pythonidae, hasConstrictionAsKillingMethod, true]
-
A.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
B.
usesConstriction
chosen
Indicates that one entity applies pressure by tightening or squeezing around another entity to restrain, control, or affect it.
-
C.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
D.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
E.
deathMethod
Indicates the specific way or means by which a death occurred.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6aa6188190af7656ff4d0e3230 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.