Triple
T2655828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gion Matsuri |
E54606
|
entity |
| Predicate | originPurpose |
P79
|
FINISHED |
| Object | to appease plague and epidemics |
—
|
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: to appease plague and epidemics | Statement: [Gion Matsuri, originPurpose, to appease plague and epidemics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originPurpose Context triple: [Gion Matsuri, originPurpose, to appease plague and epidemics]
-
A.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
originNote
Indicates a note or comment that explains the origin, source, or provenance of an entity or relationship.
-
C.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
originContext
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
E.
originAssociatedWith
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.