Triple
T37157775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan buzkashi |
E920556
|
entity |
| Predicate | animalPreparation |
P40977
|
FINISHED |
| Object | carcass is headless |
—
|
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: carcass is headless | Statement: [Afghan buzkashi, animalPreparation, carcass is headless]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animalPreparation Context triple: [Afghan buzkashi, animalPreparation, carcass is headless]
-
A.
meatPreparation
chosen
Indicates the method or process by which meat is treated, cooked, or otherwise prepared for consumption.
-
B.
fishPreparation
Indicates the method or process by which a fish is prepared (e.g., cleaned, cut, seasoned, or cooked) for consumption or use.
-
C.
sacrificedAnimal
Indicates that one entity killed or offered an animal as a sacrifice, typically for a ritual, religious, or ceremonial purpose, in relation to another entity or context.
-
D.
sacrificeAnimalType
Indicates that an entity performs or is involved in the act of sacrificing an animal of a specified type.
-
E.
preparesFoodFor
Indicates that one entity makes or cooks food intended to be eaten by another 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.