Triple
T28003949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford–Luton rivalry |
E707222
|
entity |
| Predicate | primaryVenueForLutonHomeMatches |
P201031
|
FINISHED |
| Object | Kenilworth Road |
—
|
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: Kenilworth Road | Statement: [Watford–Luton rivalry, primaryVenueForLutonHomeMatches, Kenilworth Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVenueForLutonHomeMatches Context triple: [Watford–Luton rivalry, primaryVenueForLutonHomeMatches, Kenilworth Road]
-
A.
primaryVenueForWatfordHomeMatches
Indicates that a venue serves as the main location where Watford’s home matches are played.
-
B.
LewisohnStadiumCity
Indicates that a Lewisohn Stadium is (or was) located in the specified city.
-
C.
hasHomeStadiumForFulham
Indicates that something serves as the home stadium used by Fulham for hosting its matches.
-
D.
hasHomeStadiumOfOxfordUnited
Indicates that the subject is the home stadium used by the football club Oxford United.
-
E.
homeStadiumEngland
Indicates that the specified stadium serves as the home venue for an England national team or English representative side.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 27, 2026, 7:59 p.m.