Triple
T25152271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noci |
E630108
|
entity |
| Predicate | hasLocalCuisineFeature |
P17157
|
FINISHED |
| Object | Apulian dishes |
—
|
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: Apulian dishes | Statement: [Noci, hasLocalCuisineFeature, Apulian dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCuisineFeature Context triple: [Noci, hasLocalCuisineFeature, Apulian dishes]
-
A.
cuisineFeature
chosen
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
B.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
C.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
D.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
hasCuisineRecognition
Indicates that an entity has received formal recognition, awards, or notable acknowledgment specifically for its cuisine.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 6:30 a.m.