Triple
T5866040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USF Dons |
E130395
|
entity |
| Predicate | homeCourtCapacity |
P3606
|
FINISHED |
| Object | approximately 3,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: approximately 3,000 | Statement: [USF Dons, homeCourtCapacity, approximately 3,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCourtCapacity Context triple: [USF Dons, homeCourtCapacity, approximately 3,000]
-
A.
homeArenaCapacity
chosen
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
B.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
C.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
D.
homeCourtDedicatedTo
Indicates that a particular sports venue or court is officially named for or ceremonially assigned in honor of a specific person, group, or entity.
-
E.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.