Triple
T2054753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The American Adventure |
E45647
|
entity |
| Predicate | audienceCapacity |
P15029
|
FINISHED |
| Object | large indoor theater |
—
|
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: large indoor theater | Statement: [The American Adventure, audienceCapacity, large indoor theater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceCapacity Context triple: [The American Adventure, audienceCapacity, large indoor theater]
-
A.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
B.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
D.
hasAudienceSize
chosen
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
E.
courtyardCapacity
Indicates the maximum number of entities that can be accommodated in a courtyard at the same time.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9a8518081909ba95a8ef9321f12 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.