Triple
T16199015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City Hornets |
E393146
|
entity |
| Predicate | homeGameAverageAttendanceTrend |
P52815
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Oklahoma City Hornets, homeGameAverageAttendanceTrend, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGameAverageAttendanceTrend Context triple: [Oklahoma City Hornets, homeGameAverageAttendanceTrend, high]
-
A.
averageAttendanceTrend
chosen
Indicates how the average attendance changes over time, such as increasing, decreasing, or remaining stable.
-
B.
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.
-
C.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
D.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
E.
averageAttendanceCategory
Indicates the attendance range or classification into which an entity’s typical or mean attendance level falls.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222de2db481908471b9c73d444607 |
completed | April 17, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.