Triple
T1192753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishiwada |
E25598
|
entity |
| Predicate | festivalHeldIn |
P26210
|
FINISHED |
| Object | September |
—
|
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: September | Statement: [Kishiwada, festivalHeldIn, September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalHeldIn Context triple: [Kishiwada, festivalHeldIn, September]
-
A.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
B.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
C.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
D.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
E.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd761ef08190b431b80f326d1ab2 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:45 p.m.