Triple
T26551262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天神祭 |
E671683
|
entity |
| Predicate | 国指定文化財区分 |
P146748
|
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.
isPartOfCulturalPropertyGroup
Indicates that something belongs to or is included within a defined group or collection of related cultural properties.
-
C.
culturalHeritageCategory
chosen
Indicates the classification of something according to its type or category within cultural heritage (e.g., monument, tradition, artifact).
-
D.
nationalDesignation
Indicates that an entity has been formally assigned a specific status, title, or classification by a nation or national authority.
-
E.
culturalDesignation
Indicates that an entity has been assigned a particular cultural status, label, or classification within a specific cultural or heritage context.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:47 a.m.