Triple
T19408640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leazes Stand |
E485528
|
entity |
| Predicate | homeVenueForCompetition |
P74757
|
FINISHED |
| Object | Premier League matches of Newcastle United F.C. |
—
|
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: Premier League matches of Newcastle United F.C. | Statement: [Leazes Stand, homeVenueForCompetition, Premier League matches of Newcastle United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueForCompetition Context triple: [Leazes Stand, homeVenueForCompetition, Premier League matches of Newcastle United F.C.]
-
A.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context or event.
-
B.
gameVenue
chosen
Indicates the location or facility where a game or match is held.
-
C.
homeVenueTeam2City
Indicates that a second home venue team is based in or associated with a particular city.
-
D.
homeArenaForTournament
Indicates that an arena serves as the designated home venue for a particular tournament.
-
E.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af331108190b6b25ef8f386826e |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.