Triple
T17123579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanda district |
E415529
|
entity |
| Predicate | KandaMatsuriType |
P126064
|
FINISHED |
| Object | Shinto festival |
—
|
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: Shinto festival | Statement: [Kanda district, KandaMatsuriType, Shinto festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KandaMatsuriType Context triple: [Kanda district, KandaMatsuriType, Shinto festival]
-
A.
TenjinMatsuriLocation
Indicates the location where the Tenjin Matsuri festival takes place or is held.
-
B.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
C.
KawagoeFestivalStatus
Indicates the status or condition of the Kawagoe Festival in relation to a given time or context (e.g., whether it is scheduled, ongoing, or completed).
-
D.
hasKamiType
Indicates that an entity is associated with or classified under a specific type or category of kami.
-
E.
AtsutaShrineIs
Indicates that something has the status, identity, or defining characteristics of Atsuta Shrine.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80b7e6881909f7635875549a2f1 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:36 a.m.