Triple
T24936205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kani Doraku Co., Ltd. |
E623318
|
entity |
| Predicate | operatesRestaurantType |
P81236
|
FINISHED |
| Object | specialty seafood restaurant |
—
|
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: specialty seafood restaurant | Statement: [Kani Doraku Co., Ltd., operatesRestaurantType, specialty seafood restaurant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesRestaurantType Context triple: [Kani Doraku Co., Ltd., operatesRestaurantType, specialty seafood restaurant]
-
A.
operatedDiningService
Indicates that one entity managed and provided dining or food service operations for another entity or location.
-
B.
hasRestaurantType
chosen
Indicates that an entity is associated with or classified as a particular type or category of restaurant.
-
C.
restaurantOperator
Indicates that one entity operates, manages, or runs a restaurant business associated with another entity.
-
D.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
E.
operatedEstablishmentIn
Indicates that an entity ran or managed an establishment located within a specified place or jurisdiction.
- 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_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 18, 2026, 5:30 a.m.