Triple
T9031936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phom Naga |
E216391
|
entity |
| Predicate | traditionalFoodBase |
P85784
|
FINISHED |
| Object | rice |
—
|
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: rice | Statement: [Phom Naga, traditionalFoodBase, rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFoodBase Context triple: [Phom Naga, traditionalFoodBase, rice]
-
A.
traditionalCuisine
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
B.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
C.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
D.
regionOfCulinaryImportance
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
-
E.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6a9f2c7481909b4a272183f20585 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.