Triple
T31116983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixfields Stadium |
E793115
|
entity |
| Predicate | temporaryHomeStadiumOf |
P116193
|
FINISHED |
| Object | Coventry City F.C. |
—
|
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: Coventry City F.C. | Statement: [Sixfields Stadium, temporaryHomeStadiumOf, Coventry City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryHomeStadiumOf Context triple: [Sixfields Stadium, temporaryHomeStadiumOf, Coventry City F.C.]
-
A.
homeStadiumTemporary
chosen
Indicates that a stadium serves as a team's or organization's home venue only for a limited or interim period, rather than as its permanent home stadium.
-
B.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
C.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
D.
homeTeamStadiumUsed
Indicates that a particular stadium is used as the home venue by a specified home team.
-
E.
temporaryHomeOf
Indicates that one entity serves as a non-permanent or interim place of residence or storage for another 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 9:04 p.m.