Triple
T32792107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horyuji Homotsukan |
E838655
|
entity |
| Predicate | hasVisitorAmenities |
P79291
|
FINISHED |
| Object | museum shop |
—
|
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: museum shop | Statement: [Horyuji Homotsukan, hasVisitorAmenities, museum shop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorAmenities Context triple: [Horyuji Homotsukan, hasVisitorAmenities, museum shop]
-
A.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
B.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
C.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
D.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
-
E.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:14 a.m.