Triple
T2231228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kezar Stadium |
E48768
|
entity |
| Predicate | currentCapacity |
P36396
|
FINISHED |
| Object | approximately 10,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 10,000 | Statement: [Kezar Stadium, currentCapacity, approximately 10,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentCapacity Context triple: [Kezar Stadium, currentCapacity, approximately 10,000]
-
A.
originalCapacity
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
B.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
C.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
D.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
-
E.
approximateCapacity
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06b7374819089fe643e12797bfd |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.