Triple
T27078283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warekena people |
E685521
|
entity |
| Predicate | foodProcessing |
P161825
|
FINISHED |
| Object | manioc flour production |
—
|
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: manioc flour production | Statement: [Warekena people, foodProcessing, manioc flour production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodProcessing Context triple: [Warekena people, foodProcessing, manioc flour production]
-
A.
isProcessedFood
Indicates that a food item has been altered from its natural state through industrial or mechanical methods such as refining, adding ingredients, or preserving.
-
B.
meatPreparation
Indicates the method or process by which meat is treated, cooked, or otherwise prepared for consumption.
-
C.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
D.
preparationIndustry
Indicates that an entity is involved in or associated with the industrial-scale preparation or processing of another entity.
-
E.
foodItem
Indicates that one entity is a food item that can be eaten or used as food in relation to another entity.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231742748190929446f701a0ba50 |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:32 a.m.