Triple
T8169826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitano Stadium |
E190787
|
entity |
| Predicate | seatingCapacityLeagueMatches |
P2491
|
FINISHED |
| Object | about 68,000 |
—
|
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: about 68,000 | Statement: [Metropolitano Stadium, seatingCapacityLeagueMatches, about 68,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityLeagueMatches Context triple: [Metropolitano Stadium, seatingCapacityLeagueMatches, about 68,000]
-
A.
maximumAttendanceMatch
Indicates that the match or event has reached or is constrained by its maximum allowed number of attendees.
-
B.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
C.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
D.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
E.
leagueMatchesPlayed
Indicates the number of matches an entity has participated in within a specific league competition.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4803de688190960438aa059d163b |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.