Triple
T18687621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand popular culture |
E456906
|
entity |
| Predicate | includesCuisine |
P17589
|
FINISHED |
| Object | fish and chips |
—
|
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: fish and chips | Statement: [New Zealand popular culture, includesCuisine, fish and chips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCuisine Context triple: [New Zealand popular culture, includesCuisine, fish and chips]
-
A.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
B.
hasCuisineItem
chosen
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
C.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
D.
hasCuisineRecognition
Indicates that an entity has received formal recognition, awards, or notable acknowledgment specifically for its cuisine.
-
E.
includesRegionalCuisine
Indicates that one entity incorporates or features the regional cuisine 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2e4c6081908bb958bd00d6bec9 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.