Triple
T27199492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sannō Matsuri |
E683695
|
entity |
| Predicate | alternateWith |
P163479
|
FINISHED |
| Object | Kanda Matsuri |
—
|
NE NERFINISHED |
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: Kanda Matsuri | Statement: [Sannō Matsuri, alternateWith, Kanda Matsuri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateWith Context triple: [Sannō Matsuri, alternateWith, Kanda Matsuri]
-
A.
alternativeTerminus
Indicates that something serves as another possible endpoint or final destination in place of, or in addition to, a primary terminus.
-
B.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another entity.
-
C.
alternativeImplementation
Indicates that one implementation serves as a substitute or different way of realizing the same functionality or specification as another implementation.
-
D.
alternateEnding
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
-
E.
alternativeHolder
Indicates that one entity serves as an alternative or substitute holder in place of another entity.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 9:35 a.m.