Triple
T12696982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokuon-ji |
E303358
|
entity |
| Predicate | majorAttractionFor |
P5644
|
FINISHED |
| Object | domestic tourists |
—
|
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: domestic tourists | Statement: [Rokuon-ji, majorAttractionFor, domestic tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorAttractionFor Context triple: [Rokuon-ji, majorAttractionFor, domestic tourists]
-
A.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
B.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
-
C.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
D.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.