Triple
T24936196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kani Doraku Co., Ltd. |
E623318
|
entity |
| Predicate | hasNotableSignageAt |
P114273
|
FINISHED |
| Object | Dotonbori canal area |
—
|
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: Dotonbori canal area | Statement: [Kani Doraku Co., Ltd., hasNotableSignageAt, Dotonbori canal area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSignageAt Context triple: [Kani Doraku Co., Ltd., hasNotableSignageAt, Dotonbori canal area]
-
A.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
B.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
hasTouristSignage
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
D.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
E.
hasNeonSigns
chosen
Indicates that an entity features or is adorned with neon signs as part of its visual or advertising elements.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 5:30 a.m.