Triple
T34221119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDS Arena |
E877923
|
entity |
| Predicate | seatingCapacityRugby |
P163659
|
FINISHED |
| Object | 18500 |
—
|
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: 18500 | Statement: [RDS Arena, seatingCapacityRugby, 18500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityRugby Context triple: [RDS Arena, seatingCapacityRugby, 18500]
-
A.
capacityRugby
chosen
Indicates that an entity has a specified seating or attendance capacity for hosting rugby events or matches.
-
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.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7108232488190a8c33ae6c0246929 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.