Triple
T35301599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quips |
E1019519
|
entity |
| Predicate | hasHomeFootballStadium |
P16388
|
FINISHED |
| Object | Carl A. Aschman Stadium |
—
|
NE NERFINISHED |
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: Carl A. Aschman Stadium | Statement: [Quips, hasHomeFootballStadium, Carl A. Aschman Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFootballStadium Context triple: [Quips, hasHomeFootballStadium, Carl A. Aschman Stadium]
-
A.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
B.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
C.
isLocalStadiumFor
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
-
D.
hasTeamStadium
chosen
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
E.
homeStadiumNamedAfter
Indicates that a stadium serving as a team's home venue bears the name of a specified person, organization, or entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:03 p.m.