Triple
T32368224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington & Jefferson Presidents football team |
E827055
|
entity |
| Predicate | usesStadiumForHomeGames |
P174697
|
FINISHED |
| Object | Cameron 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: Cameron Stadium | Statement: [Washington & Jefferson Presidents football team, usesStadiumForHomeGames, Cameron Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStadiumForHomeGames Context triple: [Washington & Jefferson Presidents football team, usesStadiumForHomeGames, Cameron Stadium]
-
A.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
homeTeamStadiumUsed
Indicates that a particular stadium is used as the home venue by a specified home team.
-
C.
homeStadiumUsedForEvent
Indicates that a particular stadium, serving as a team or organization's home venue, is used to host a specific event.
-
D.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
E.
isLocalStadiumFor
chosen
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 12:50 a.m.