Triple
T37241628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aka people |
E923725
|
entity |
| Predicate | foodSharingNorm |
P187335
|
FINISHED |
| Object | strong sharing of meat and gathered foods |
—
|
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: strong sharing of meat and gathered foods | Statement: [Aka people, foodSharingNorm, strong sharing of meat and gathered foods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodSharingNorm Context triple: [Aka people, foodSharingNorm, strong sharing of meat and gathered foods]
-
A.
sharesFoodWith
Indicates that one entity gives or divides its food with another entity so that both can eat from it.
-
B.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
C.
commonlyConsumedAt
Indicates that one entity is typically eaten or drunk during, or in association with, a particular time, event, or context.
-
D.
isOftenEaten
Indicates that the subject is frequently consumed as food by some agent or group.
-
E.
isTypicallyEatenWith
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb41333b548190912cb238ffc271c9 |
completed | May 6, 2026, 1:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.