Triple
T31116924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aston Villa–Coventry City rivalry |
E793113
|
entity |
| Predicate | seeAlsoClub |
P102426
|
FINISHED |
| Object | Aston Villa 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: Aston Villa F.C. | Statement: [Aston Villa–Coventry City rivalry, seeAlsoClub, Aston Villa F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeAlsoClub Context triple: [Aston Villa–Coventry City rivalry, seeAlsoClub, Aston Villa F.C.]
-
A.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
B.
relatedToClub
chosen
Indicates that there is an association or connection between an entity and a club, without specifying the exact nature of that relationship.
-
C.
associatedClubSport
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
D.
participatingClubsFrom
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
-
E.
affiliatedClubOf
Indicates that one entity is a club with which another entity is formally associated or connected.
- 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_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.