Triple
T6401741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrier Dome |
E144078
|
entity |
| Predicate | seatingCapacityLacrosse |
P2491
|
FINISHED |
| Object | about 35,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: about 35,000 | Statement: [Carrier Dome, seatingCapacityLacrosse, about 35,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityLacrosse Context triple: [Carrier Dome, seatingCapacityLacrosse, about 35,000]
-
A.
homeVenueLacrosse
Indicates that a specified venue serves as the designated home location where a particular lacrosse team hosts its home games or matches.
-
B.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
typicalSeatingCapacityLowerBound
Indicates the minimum number of seats that an entity is typically designed or expected to provide.
-
D.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
-
E.
infieldCapacity
Indicates the maximum number of entities that can be accommodated within a defined infield area or region.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068ade8c881908a0472f1de6b7c21 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.