Triple
T37060762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天野川 |
E917316
|
entity |
| Predicate | 関連観光 |
P33214
|
FINISHED |
| Object | 七夕伝説をテーマにした観光資源となっている |
—
|
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: 七夕伝説をテーマにした観光資源となっている | Statement: [天野川, 関連観光, 七夕伝説をテーマにした観光資源となっている]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連観光 Context triple: [天野川, 関連観光, 七夕伝説をテーマにした観光資源となっている]
-
A.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
B.
tourismFeature
chosen
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
C.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a tour.
-
D.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
E.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.