Triple
T21394469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozan-ji |
E527742
|
entity |
| Predicate | Chōjū-gigaStatus |
P143805
|
FINISHED |
| Object | National Treasure of Japan |
—
|
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: National Treasure of Japan | Statement: [Kozan-ji, Chōjū-gigaStatus, National Treasure of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Chōjū-gigaStatus Context triple: [Kozan-ji, Chōjū-gigaStatus, National Treasure of Japan]
-
A.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
B.
TaishoNumber
Indicates that an entity is associated with a specific Taisho catalog or numbering system identifier.
-
C.
NorbulingkaStatus
Indicates the current condition, designation, or preservation state associated with Norbulingka.
-
D.
Chi Chi
Indicates a relationship or action involving an entity named "Chi Chi," such as interaction, association, or effect directed to or from Chi Chi.
-
E.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
- F. None of above. chosen
Provenance (4 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b117d8c881908b823c1212b5b919 |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:13 p.m.