Triple
T14766895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Green Tennis Center |
E347018
|
entity |
| Predicate | seatingCapacityOfCourt2 |
P2491
|
FINISHED |
| Object | 4000 |
—
|
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: 4000 | Statement: [Olympic Green Tennis Center, seatingCapacityOfCourt2, 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityOfCourt2 Context triple: [Olympic Green Tennis Center, seatingCapacityOfCourt2, 4000]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
centreCourtName
Indicates the name assigned to the central court associated with a particular venue or event.
-
C.
hasSecondaryHallCapacity
Indicates that an entity possesses a specified capacity for a secondary hall or auxiliary event space.
-
D.
venueCapacityApproximate
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
E.
hasHeadCourt
Indicates that an entity (such as an organization or jurisdiction) is associated with a primary or central court that serves as its main judicial authority.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f576c881909da70627f5897c94 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.