Triple
T14194848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laing |
E351809
|
entity |
| Predicate | subcuisine |
P70749
|
FINISHED |
| Object | Bicolano cuisine |
—
|
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: Bicolano cuisine | Statement: [Laing, subcuisine, Bicolano cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subcuisine Context triple: [Laing, subcuisine, Bicolano cuisine]
-
A.
cuisineSubtype
chosen
Indicates that one cuisine is a more specific subtype or variant within the broader category of another cuisine.
-
B.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
C.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
D.
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.
-
E.
traditionalFoodBase
Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with another entity.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61e1fbd48190a4864fa4443f8f29 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:04 a.m.