Triple
T30823004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumida River Fireworks Festival |
E784978
|
entity |
| Predicate | typicalAttendanceRange |
P87333
|
FINISHED |
| Object | around one million spectators |
—
|
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: around one million spectators | Statement: [Sumida River Fireworks Festival, typicalAttendanceRange, around one million spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttendanceRange Context triple: [Sumida River Fireworks Festival, typicalAttendanceRange, around one million spectators]
-
A.
hasTypicalAttendance
chosen
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
-
B.
averageAttendanceCategory
Indicates the attendance range or classification into which an entity’s typical or mean attendance level falls.
-
C.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
averageAttendanceLow
Indicates that the typical or mean attendance level for an event, group, or activity is below a defined or expected threshold.
-
E.
averageAttendancePerGame
Indicates the typical number of attendees present at each individual game over a given period.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:44 p.m.