Triple
T23301687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 法隆寺 |
E590318
|
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.
culturalHeritageCategory
Indicates the classification of something according to its type or category within cultural heritage (e.g., monument, tradition, artifact).
-
C.
hasCulturalProtection
Indicates that an entity is subject to legal or formal measures intended to preserve and safeguard its cultural value or heritage.
-
D.
culturalHeritageOf
Indicates that something serves as the cultural heritage belonging to, originating from, or strongly associated with a particular entity or group.
-
E.
culturalDesignation
chosen
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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.