Triple
T34099139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Stadium |
E874515
|
entity |
| Predicate | recordAttendanceOver |
P194716
|
FINISHED |
| Object | 110000 |
—
|
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: 110000 | Statement: [Ohio Stadium, recordAttendanceOver, 110000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordAttendanceOver Context triple: [Ohio Stadium, recordAttendanceOver, 110000]
-
A.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
B.
recordAttendanceYear
Indicates that an entity’s attendance is recorded or tracked for a specific calendar or academic year.
-
C.
attendanceRecordMatch
Indicates that two attendance records correspond to the same underlying event, person, or time entry according to defined matching criteria.
-
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.
attendanceFeature
Indicates that an entity provides or is associated with a feature or functionality related to attendance (such as tracking, managing, or recording attendance).
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: May 1, 2026, 1:53 a.m.