Triple
T3157234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ullevi Stadium |
E66012
|
entity |
| Predicate | hasRecordAttendance |
P14458
|
FINISHED |
| Object | over 70000 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: over 70000 spectators | Statement: [Ullevi Stadium, hasRecordAttendance, over 70000 spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordAttendance Context triple: [Ullevi Stadium, hasRecordAttendance, over 70000 spectators]
-
A.
recordAttendance
chosen
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
B.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
C.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
D.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
E.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5eafa4c8190a65cc1312823144c |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.