Triple
T24936182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kani Doraku Co., Ltd. |
E623318
|
entity |
| Predicate | hasFlagshipRestaurant |
P43978
|
FINISHED |
| Object | Kani Doraku Dotonbori Honten |
—
|
NE NERFINISHED |
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: Kani Doraku Dotonbori Honten | Statement: [Kani Doraku Co., Ltd., hasFlagshipRestaurant, Kani Doraku Dotonbori Honten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlagshipRestaurant Context triple: [Kani Doraku Co., Ltd., hasFlagshipRestaurant, Kani Doraku Dotonbori Honten]
-
A.
hasRestaurantType
Indicates that an entity is associated with or classified as a particular type or category of restaurant.
-
B.
hasFlagshipIn
chosen
Indicates that an entity designates a particular location or branch as its primary or flagship presence.
-
C.
hasRestaurant
Indicates that one entity possesses, operates, or contains a restaurant associated with it.
-
D.
isDiningDestination
Indicates that a place serves as a destination where people go specifically to eat meals or dine.
-
E.
rivalRestaurantOf
Indicates that one restaurant competes with another restaurant in the same market or customer base.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:30 a.m.