Triple
T28003976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford–Luton rivalry |
E707222
|
entity |
| Predicate | impactOnClubs |
P156643
|
FINISHED |
| Object | influences fan identity |
—
|
LITERAL FINISHED |
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: influences fan identity | Statement: [Watford–Luton rivalry, impactOnClubs, influences fan identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnClubs Context triple: [Watford–Luton rivalry, impactOnClubs, influences fan identity]
-
A.
influenceOnClub
chosen
Indicates that one entity has an effect on, shapes, or alters the state, performance, or direction of a club.
-
B.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
C.
impactOnField
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
-
D.
privateClub
Indicates that an entity is a club or organization whose membership or access is restricted to selected or approved individuals rather than being open to the general public.
-
E.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 7:59 p.m.