Triple
T37061307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 宇治市 |
E917330
|
entity |
| Predicate | 世界遺産分類 |
P7642
|
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.
UNESCOClassification
Indicates the official category or status assigned to something under UNESCO’s classification system (e.g., World Heritage, Intangible Cultural Heritage, biosphere reserve).
-
B.
UNESCOSiteType
chosen
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
-
C.
UNESCOHeritage
Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
-
D.
isInUNESCOSiteCategory
Indicates that an entity belongs to, or is classified under, a specific UNESCO World Heritage Site category.
-
E.
UNESCODesignationBy
Indicates that an entity has been designated or recognized with a specific UNESCO status by a particular UNESCO body or authority.
- 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.