Triple
T33213051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Clippers |
E850210
|
entity |
| Predicate | homeCapacityBasketball |
P3606
|
FINISHED |
| Object | approximately 10000 |
—
|
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 10000 | Statement: [Ontario Clippers, homeCapacityBasketball, approximately 10000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCapacityBasketball Context triple: [Ontario Clippers, homeCapacityBasketball, approximately 10000]
-
A.
capacityForBasketball
Indicates the ability or suitability of an entity to play or perform well in basketball.
-
B.
homeArenaCapacity
chosen
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
homeBasketballArena
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
-
D.
basketHeight
Indicates the vertical distance from the ground or reference surface to the top or rim of a basket.
-
E.
usesStandardBasketballCourt
Indicates that the subject conducts its basketball-related activities on a regulation-size, standard-layout basketball court.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:30 a.m.