Triple
T7300395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dotonbori |
E167833
|
entity |
| Predicate | famousForCuisine |
P59511
|
FINISHED |
| Object | takoyaki |
—
|
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: takoyaki | Statement: [Dotonbori, famousForCuisine, takoyaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousForCuisine Context triple: [Dotonbori, famousForCuisine, takoyaki]
-
A.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
isNationalDishOf
Indicates that a particular food is officially or culturally recognized as the national dish of a specific country or region.
-
D.
haveCuisine
chosen
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
E.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebaef4a081908fadc6d5e2621e80 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.