Triple
T7445415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radio City Christmas Spectacular |
E171863
|
entity |
| Predicate | mainVenueCapacity |
P72212
|
FINISHED |
| Object | over 5900 seats |
—
|
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 5900 seats | Statement: [Radio City Christmas Spectacular, mainVenueCapacity, over 5900 seats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVenueCapacity Context triple: [Radio City Christmas Spectacular, mainVenueCapacity, over 5900 seats]
-
A.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
B.
concertCapacity
Indicates the maximum number of people that can be accommodated at a concert event or venue.
-
C.
mainHallCapacity
chosen
Indicates the maximum number of people that the main hall can accommodate at one time.
-
D.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
-
E.
typicalSeatingCapacityLowerBound
Indicates the minimum number of seats that an entity is typically designed or expected to provide.
- 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_69c68a65402881908f7869368eb746fb |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f37054388190a6cb4c0db2ca6014 |
completed | March 27, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.