Triple
T9971072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakata Gion Yamakasa |
E196203
|
entity |
| Predicate | heritageStatusYear |
P13050
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Hakata Gion Yamakasa, heritageStatusYear, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageStatusYear Context triple: [Hakata Gion Yamakasa, heritageStatusYear, 1979]
-
A.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
B.
heritageRevelationYear
Indicates the year in which a particular heritage status, designation, or significance was formally revealed, recognized, or made public.
-
C.
heritageDesignationYear
chosen
Indicates the year in which something was formally granted a particular heritage designation or status.
-
D.
heritageSince
Indicates that a heritage status, tradition, or cultural legacy has been in effect or recognized starting from a specific point in time.
-
E.
heritageStatusChange
Indicates a change in an entity’s cultural or historical heritage designation, such as being newly listed, upgraded, downgraded, or removed from heritage status.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.