Triple
T8278067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2018 |
E193595
|
entity |
| Predicate | stadiumCapacityForMatch |
P27055
|
FINISHED |
| Object | over 73000 |
—
|
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: over 73000 | Statement: [MLS Cup 2018, stadiumCapacityForMatch, over 73000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stadiumCapacityForMatch Context triple: [MLS Cup 2018, stadiumCapacityForMatch, over 73000]
-
A.
stadiumCapacityContext
chosen
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
B.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
C.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
maximumAttendanceMatch
Indicates that the match or event has reached or is constrained by its maximum allowed number of attendees.
-
E.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ebb6b88190bc777b8bd72fcdbc |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.