Triple
T10116052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Anthem |
E218359
|
entity |
| Predicate | hasStandingRoomCapacity |
P89353
|
FINISHED |
| Object | up to 6000 |
—
|
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: up to 6000 | Statement: [The Anthem, hasStandingRoomCapacity, up to 6000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandingRoomCapacity Context triple: [The Anthem, hasStandingRoomCapacity, up to 6000]
-
A.
hasStandingCapacity
Indicates that an entity is capable of maintaining or supporting a specified condition, function, or load on an ongoing basis.
-
B.
standingCapacity
chosen
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
E.
hasReadingRoomCapacity
Indicates the maximum number of people that can be accommodated in a reading room at one 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd162fac0819084c74947c1f6688e |
completed | April 2, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.