Triple
T3301777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sporting Kansas City |
E69349
|
entity |
| Predicate | homeCapacityType |
P13867
|
FINISHED |
| Object | soccer-specific stadium |
—
|
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: soccer-specific stadium | Statement: [Sporting Kansas City, homeCapacityType, soccer-specific stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCapacityType Context triple: [Sporting Kansas City, homeCapacityType, soccer-specific stadium]
-
A.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
hostsUnitType
chosen
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
D.
homeKitType
Indicates the specific HomeKit category or type assigned to a device or accessory within the HomeKit ecosystem.
-
E.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a7d224819080d9a638e08bb8a8 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.