Triple
T25577917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tees–Wear derby |
E641161
|
entity |
| Predicate | hasHomeGroundForSunderland |
P163018
|
FINISHED |
| Object | Stadium of Light |
—
|
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: Stadium of Light | Statement: [Tees–Wear derby, hasHomeGroundForSunderland, Stadium of Light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundForSunderland Context triple: [Tees–Wear derby, hasHomeGroundForSunderland, Stadium of Light]
-
A.
hasHomeGroundForHibs
Indicates that a location serves as the designated home ground (home stadium) for the Hibernian Football Club (Hibs).
-
B.
hasHomeGroundForFulham
Indicates that something serves as the designated home ground or home venue for Fulham.
-
C.
hasHomeGroundForLancashireMatches
Indicates that a location serves as the designated home venue where Lancashire’s matches are played.
-
D.
hasHomeGroundForBrentford
Indicates that one entity serves as the designated home ground (home stadium/venue) for the Brentford team.
-
E.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 21, 2026, 4:02 p.m.