Triple
T31116909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aston Villa–Coventry City rivalry |
E793113
|
entity |
| Predicate | clubFromCoventry |
P171336
|
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: [Aston Villa–Coventry City rivalry, clubFromCoventry, Coventry City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubFromCoventry Context triple: [Aston Villa–Coventry City rivalry, clubFromCoventry, Coventry City F.C.]
-
A.
coventryCityMajorTrophyStatus
Indicates whether Coventry City Football Club has won any major trophies and, if so, the status of those achievements.
-
B.
clubsCounty
Indicates that a club is located in, associated with, or belongs to a particular county.
-
C.
clubNumberAtSportingCP
Indicates the jersey number a player wore while playing for Sporting CP.
-
D.
rugbyLeagueClub
Indicates that one entity is a rugby league club associated with, owned by, or representing the other entity.
-
E.
associationFootballClub
Indicates that the subject is an association football (soccer) club, i.e., an organized team entity that plays the sport of association football.
- F. None of above. chosen
Provenance (4 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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:04 p.m.