Triple
T20556307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grünwalder Stadion |
E504728
|
entity |
| Predicate | maximumAttendanceRecord |
P140544
|
FINISHED |
| Object | 58000 |
—
|
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: 58000 | Statement: [Grünwalder Stadion, maximumAttendanceRecord, 58000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAttendanceRecord Context triple: [Grünwalder Stadion, maximumAttendanceRecord, 58000]
-
A.
maximumAttendanceMatch
Indicates that the match or event has reached or is constrained by its maximum allowed number of attendees.
-
B.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
C.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
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.
hasTypicalAttendance
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5de9c008190b8620628fb285e90 |
completed | April 20, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:38 a.m.