Triple
T19966207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laos and Cambodia |
E479939
|
entity |
| Predicate | shareCuisineCharacteristic |
P17157
|
FINISHED |
| Object | rice-based diet |
—
|
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-based diet | Statement: [Laos and Cambodia, shareCuisineCharacteristic, rice-based diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareCuisineCharacteristic Context triple: [Laos and Cambodia, shareCuisineCharacteristic, rice-based diet]
-
A.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
B.
cuisineFeature
chosen
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
C.
cultureCharacteristic
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
D.
foodCulture
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
-
E.
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.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc4f47c8190a721f5e488150d81 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.