Triple
T28003796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rookery Stand |
E707217
|
entity |
| Predicate | homeSupportersStandFor |
P42456
|
FINISHED |
| Object | Watford 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: Watford F.C. | Statement: [Rookery Stand, homeSupportersStandFor, Watford F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSupportersStandFor Context triple: [Rookery Stand, homeSupportersStandFor, Watford F.C.]
-
A.
homeSupportersSectionFor
chosen
Indicates that a particular seating section is designated for the home team's supporters at a sporting event or venue.
-
B.
supportersDescription
Indicates that one entity provides support, endorsement, or backing to another entity.
-
C.
hasSupportersIn
Indicates that an entity is backed or endorsed by people or groups located within a specified place or region.
-
D.
homeStandOf
Indicates that a particular venue or location serves as the primary home stadium or home ground for a sports team or organization.
-
E.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:58 p.m.