Triple
T729784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardinia |
E14804
|
entity |
| Predicate | traditionalDish |
P19483
|
FINISHED |
| Object | porceddu (roast suckling pig) |
—
|
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: porceddu (roast suckling pig) | Statement: [Sardinia, traditionalDish, porceddu (roast suckling pig)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDish Context triple: [Sardinia, traditionalDish, porceddu (roast suckling pig)]
-
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.
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.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
traditionalOrigin
Indicates that something comes from, or is rooted in, a long-established cultural or customary source or practice.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f9b7608190bf97c8418a26e632 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a66658948190bdae6e521951954f |
completed | March 1, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:37 p.m.