Triple
T512266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Michigan |
E10631
|
entity |
| Predicate | MichiganStadiumCapacity |
P3507
|
FINISHED |
| Object | over 100,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: over 100,000 | Statement: [University of Michigan, MichiganStadiumCapacity, over 100,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MichiganStadiumCapacity Context triple: [University of Michigan, MichiganStadiumCapacity, over 100,000]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
-
D.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
-
E.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f16768c081909d05537ff070868b |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edff001c81909182a7e26c6dc51b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.