Triple
T19050191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Entertainment Expo |
E466236
|
entity |
| Predicate | peakAttendanceApprox |
P23195
|
FINISHED |
| Object | over 70,000 attendees |
—
|
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: over 70,000 attendees | Statement: [Electronic Entertainment Expo, peakAttendanceApprox, over 70,000 attendees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakAttendanceApprox Context triple: [Electronic Entertainment Expo, peakAttendanceApprox, over 70,000 attendees]
-
A.
peakDayAttendance
chosen
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
hasTypicalAttendance
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
-
D.
homeAttendanceRecord
Indicates that an entity’s record or log of attendance is specifically associated with events or activities held at its home venue or location.
-
E.
estimatedCumulativeAttendance
Indicates the total number of attendees expected to have been present over a period of time, aggregated up to a given point.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc018d8c819080525ad104a85fe2 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.