Triple
T1917730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival of Sacrifice |
E40055
|
entity |
| Predicate | meatDistribution |
P11838
|
FINISHED |
| Object | one-third for the family |
—
|
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: one-third for the family | Statement: [Festival of Sacrifice, meatDistribution, one-third for the family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meatDistribution Context triple: [Festival of Sacrifice, meatDistribution, one-third for the family]
-
A.
meatDistributionRule
chosen
Indicates the rule or policy that governs how meat is allocated, portioned, or distributed among recipients or locations.
-
B.
notableMeatProduct
Indicates that one entity is a meat-based product that is especially prominent, well-known, or significant in relation to the other entity.
-
C.
typicalMeat
Indicates that something is commonly or characteristically used or regarded as meat in a given context.
-
D.
meatQuality
Indicates the assessed level or characteristics of quality associated with a given piece or type of meat.
-
E.
commonMeatCut
Indicates that two items are the same or equivalent cut of meat, or that an item belongs to a standard, commonly recognized meat cut category.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2107fe48190bafff825f1f805ad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.