Triple
T33018978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Pyramid |
E844851
|
entity |
| Predicate | seatingCapacityForVolleyball |
P160660
|
FINISHED |
| Object | about 5,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 5,000 | Statement: [Walter Pyramid, seatingCapacityForVolleyball, about 5,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityForVolleyball Context triple: [Walter Pyramid, seatingCapacityForVolleyball, about 5,000]
-
A.
volleyballCapacity
chosen
Indicates the maximum number of people or participants that can be accommodated for playing or watching volleyball in a given context.
-
B.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
C.
venueCapacityApproximate
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
D.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
-
E.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:23 a.m.