Triple
T22271605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marriott Center |
E550491
|
entity |
| Predicate | formerSeatingCapacityBasketball |
P54210
|
FINISHED |
| Object | over 22,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: over 22,000 | Statement: [Marriott Center, formerSeatingCapacityBasketball, over 22,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSeatingCapacityBasketball Context triple: [Marriott Center, formerSeatingCapacityBasketball, over 22,000]
-
A.
capacityForBasketball
Indicates the ability or suitability of an entity to play or perform well in basketball.
-
B.
replacedAsPrimaryBasketballVenueBy
Indicates that one basketball venue ceased to be the main or primary location for games or events and was succeeded in that role by another venue.
-
C.
formerStadiumCapacityApprox
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
-
D.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
E.
previousNumberOfSeats
chosen
Indicates the number of seats an entity had before a change or update in its seating count.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141c056cc819088dae6f2b9a1d526 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.