Triple
T19446789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham F.C. vs Queens Park Rangers F.C. |
E486497
|
entity |
| Predicate | hasHomeStadiumForQPR |
P2696
|
FINISHED |
| Object | Loftus 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: Loftus Road | Statement: [Fulham F.C. vs Queens Park Rangers F.C., hasHomeStadiumForQPR, Loftus Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumForQPR Context triple: [Fulham F.C. vs Queens Park Rangers F.C., hasHomeStadiumForQPR, Loftus Road]
-
A.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
B.
hasHomeGroundForHibs
Indicates that a location serves as the designated home ground (home stadium) for the Hibernian Football Club (Hibs).
-
C.
hasHomeStadiumInDerby
Indicates that an entity’s home stadium is located in the city or area of Derby.
-
D.
homeStadiumOf
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
hasHomeStadiumOfOxfordUnited
Indicates that the subject is the home stadium used by the football club Oxford United.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338a22608190bb31a1690ca0dab6 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.