Triple
T22851234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eromba |
E566359
|
entity |
| Predicate | usesFermentedProduct |
P149950
|
FINISHED |
| Object | ngari (fermented fish) |
—
|
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: ngari (fermented fish) | Statement: [Eromba, usesFermentedProduct, ngari (fermented fish)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFermentedProduct Context triple: [Eromba, usesFermentedProduct, ngari (fermented fish)]
-
A.
fermentedFood
Indicates that one entity is a food item that has been produced or altered through a fermentation process involving microorganisms.
-
B.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified entity.
-
C.
usesBottleFermentation
Indicates that a process or product involves carrying out fermentation inside a sealed bottle as part of its production.
-
D.
coFermentationAllowed
Indicates that multiple substances are permitted to be fermented together in a single combined fermentation process.
-
E.
fermentationAgent
Indicates that one entity serves as the agent or catalyst that carries out the fermentation process on 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:36 p.m.