Triple
T15901637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapampangan cuisine |
E385602
|
entity |
| Predicate | signatureDessert |
P120982
|
FINISHED |
| Object | sans rival |
—
|
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: sans rival | Statement: [Kapampangan cuisine, signatureDessert, sans rival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureDessert Context triple: [Kapampangan cuisine, signatureDessert, sans rival]
-
A.
signatureToppingStyle
Indicates the distinctive or characteristic way toppings are arranged or combined for a particular item.
-
B.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
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.
signatureItem
Indicates that an entity is a component or element that forms part of another entity’s signature (such as a defining list, pattern, or parameter set).
-
E.
signType
Indicates the specific category or kind of sign involved in the relationship or action.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:52 a.m.