Triple
T194907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD Garden |
E3797
|
entity |
| Predicate | capacityBasketball |
P3606
|
FINISHED |
| Object | approximately 19,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 19,000 | Statement: [TD Garden, capacityBasketball, approximately 19,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityBasketball Context triple: [TD Garden, capacityBasketball, approximately 19,000]
-
A.
representsInBasketball
Indicates that one entity serves as an official representative (such as an agent, delegate, or spokesperson) for another entity specifically in the context of basketball.
-
B.
homeArenaCapacity
chosen
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
D.
ballType
Indicates the specific category or kind of ball associated with an entity.
-
E.
homeBasketballArena
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.