Triple
T30317029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanabata |
E771084
|
entity |
| Predicate | hasMajorFestivalLocation |
P26210
|
FINISHED |
| Object | Sendai, Miyagi Prefecture |
—
|
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: Sendai, Miyagi Prefecture | Statement: [Tanabata, hasMajorFestivalLocation, Sendai, Miyagi Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorFestivalLocation Context triple: [Tanabata, hasMajorFestivalLocation, Sendai, Miyagi Prefecture]
-
A.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
B.
isMajorTourismEventFor
Indicates that an event is a primary or highly significant attraction for tourism in relation to a particular place or entity.
-
C.
festivalHeldIn
chosen
Indicates that a festival takes place or is hosted at a specific location or venue.
-
D.
locatedInFestivalCity
Indicates that an entity is situated within or belongs to a city that is designated as a festival city.
-
E.
hasFestivalSite
Indicates that a location or site is designated or used as the venue where a festival takes place.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: April 29, 2026, 7:51 p.m.