Triple
T34531918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemson Tigers |
E886560
|
entity |
| Predicate | playsHomeFootballGamesAt |
P91575
|
FINISHED |
| Object | Memorial 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: Memorial Stadium | Statement: [Clemson Tigers, playsHomeFootballGamesAt, Memorial Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsHomeFootballGamesAt Context triple: [Clemson Tigers, playsHomeFootballGamesAt, Memorial Stadium]
-
A.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
B.
playsSelectHomeGamesAt
chosen
Indicates that an entity (typically a sports team) holds some or all of its designated home games at a specified venue or location.
-
C.
playsAssociationFootballIn
Indicates that an entity participates in playing association football (soccer) within or for a specified place, organization, or context.
-
D.
featuresHomeAndAwayGames
Indicates that the subject includes or schedules both home and away games for the relevant participants.
-
E.
playsHomeConferenceGamesIn
Indicates that a team plays its home conference games at a specified location or venue.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 2:02 a.m.