Triple
T634983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T Stadium |
E16603
|
entity |
| Predicate | expandableCapacityAmericanFootball |
P9426
|
FINISHED |
| Object | 100000 |
—
|
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: 100000 | Statement: [AT&T Stadium, expandableCapacityAmericanFootball, 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandableCapacityAmericanFootball Context triple: [AT&T Stadium, expandableCapacityAmericanFootball, 100000]
-
A.
expandedCapacity
chosen
Indicates that an entity’s capacity has been increased beyond its previous or standard level.
-
B.
NFLTeam
Indicates a relationship where an entity is identified as a professional American football team that competes in the National Football League.
-
C.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
D.
expansionFromPreviousSeason
Indicates that the current season represents an expansion or enlargement relative to the immediately preceding season.
-
E.
expansionTeamIn
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.