Triple
T17670757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palembang cuisine |
E440513
|
entity |
| Predicate | signatureCondiment |
P128488
|
FINISHED |
| Object | cuko sauce |
—
|
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: cuko sauce | Statement: [Palembang cuisine, signatureCondiment, cuko sauce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureCondiment Context triple: [Palembang cuisine, signatureCondiment, cuko sauce]
-
A.
signatureToppingStyle
Indicates the distinctive or characteristic way toppings are arranged or combined for a particular item.
-
B.
signatureDessert
Indicates that a particular dessert is the distinctive or hallmark dessert specially associated with a given entity (such as a person, restaurant, or region).
-
C.
signatureDrink
Indicates that a particular drink is the characteristic or specially associated beverage of an entity (such as a person, venue, or brand).
-
D.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
E.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f68a038819084828ff73bcf1fcc |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:59 a.m.