Triple
T12614140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikage-sai at Shimogamo Shrine |
E301207
|
entity |
| Predicate | eventSequenceRole |
P4073
|
FINISHED |
| Object | pre-festival ceremony |
—
|
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: pre-festival ceremony | Statement: [Mikage-sai at Shimogamo Shrine, eventSequenceRole, pre-festival ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventSequenceRole Context triple: [Mikage-sai at Shimogamo Shrine, eventSequenceRole, pre-festival ceremony]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
engagementRole
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement or interaction.
-
C.
significantEventRole
Indicates that an entity plays an important or defining role in a particular significant event.
-
D.
successorStateRole
Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
-
E.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.