Triple
T28003948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford–Luton rivalry |
E707222
|
entity |
| Predicate | primaryVenueForWatfordHomeMatches |
P201011
|
FINISHED |
| Object | Vicarage 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: Vicarage Road | Statement: [Watford–Luton rivalry, primaryVenueForWatfordHomeMatches, Vicarage Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVenueForWatfordHomeMatches Context triple: [Watford–Luton rivalry, primaryVenueForWatfordHomeMatches, Vicarage Road]
-
A.
hasHomeStadiumForFulham
Indicates that something serves as the home stadium used by Fulham for hosting its matches.
-
B.
hasHomeStadiumOfOxfordUnited
Indicates that the subject is the home stadium used by the football club Oxford United.
-
C.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context or event.
-
D.
homeVenueAppearances
Indicates the number of times an entity has appeared or performed at its designated home venue.
-
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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: April 27, 2026, 7:59 p.m.