Triple
T6769056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle Mile (1954 race) |
E154996
|
entity |
| Predicate | spectatorAttendance |
P26094
|
FINISHED |
| Object | over 30,000 |
—
|
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 30,000 | Statement: [Miracle Mile (1954 race), spectatorAttendance, over 30,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorAttendance Context triple: [Miracle Mile (1954 race), spectatorAttendance, over 30,000]
-
A.
fanAttendance
chosen
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
B.
spectatorSport
Indicates that an activity is primarily performed for the enjoyment of an audience watching rather than for direct participation.
-
C.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
D.
spectatorType
Indicates the role or category of a spectator in relation to an event or activity.
-
E.
averageAttendanceHigh
Indicates that the typical or mean attendance level for an event, venue, or activity is considered high relative to a defined standard or threshold.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d232d1f08190bc30c0f24f28c475 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.