Triple
T23458065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Stand |
E567987
|
entity |
| Predicate | locatedAtStadiumOfClub |
P152356
|
FINISHED |
| Object | Doncaster Rovers 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: Doncaster Rovers F.C. | Statement: [North Stand, locatedAtStadiumOfClub, Doncaster Rovers F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtStadiumOfClub Context triple: [North Stand, locatedAtStadiumOfClub, Doncaster Rovers F.C.]
-
A.
homeStadiumLocatedIn
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
-
B.
homeStadiumSituatedOn
Indicates that a team's home stadium is physically located on or within the grounds of a specified site or area.
-
C.
leagueVenue
Indicates that a particular venue is used as the location where a league holds its games or events.
-
D.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
parentClubStadium
Indicates that a stadium serves as the home venue associated with a particular parent club.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a69904588190b44c84021e94ae63 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:53 p.m.