Triple
T28813471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 庄川 |
E727576
|
entity |
| Predicate | 関連文化財・景観指定 |
P9473
|
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.
culturalProperty
Indicates that something is recognized or treated as a cultural property, typically denoting legal or heritage status tied to cultural significance.
-
B.
culturalDesignation
chosen
Indicates that an entity has been assigned a particular cultural status, label, or classification within a specific cultural or heritage context.
-
C.
culturalHeritageOf
Indicates that something serves as the cultural heritage belonging to, originating from, or strongly associated with a particular entity or group.
-
D.
isPartOfCulturalPropertyGroup
Indicates that something belongs to or is included within a defined group or collection of related cultural properties.
-
E.
UNESCOWorldHeritageSiteRelated
Indicates a relationship where one entity is designated as, part of, or otherwise officially associated with a UNESCO World Heritage Site.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.