Triple
T25340966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide 500 |
E635410
|
entity |
| Predicate | spectatorAttendanceRecord |
P86916
|
FINISHED |
| Object | over 250000 across event |
—
|
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 250000 across event | Statement: [Adelaide 500, spectatorAttendanceRecord, over 250000 across event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorAttendanceRecord Context triple: [Adelaide 500, spectatorAttendanceRecord, over 250000 across event]
-
A.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
B.
spectatorsFrom
Indicates that one or more spectators originate from, are associated with, or come to an event from a particular place or source.
-
C.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
D.
estimatedCumulativeAttendance
chosen
Indicates the total number of attendees expected to have been present over a period of time, aggregated up to a given point.
-
E.
recordAttendanceCompetition
Indicates that an entity records or logs attendance information for a competition or competitive event.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b6672881909d3257dc6b52caa3 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.