Triple
T32929772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL Sports City |
E842368
|
entity |
| Predicate | capacityOfMainStadium |
P13599
|
FINISHED |
| Object | approximately 87000 |
—
|
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: approximately 87000 | Statement: [KL Sports City, capacityOfMainStadium, approximately 87000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityOfMainStadium Context triple: [KL Sports City, capacityOfMainStadium, approximately 87000]
-
A.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
B.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
C.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
D.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
E.
keyStadium
Indicates that a stadium serves as the primary or main venue associated with a particular entity (such as a team, event, or organization).
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d104151c8190b0a9090ac766468f |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.