Triple
T27466614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Diamonds |
E693191
|
entity |
| Predicate | clubHomeStadiumLocation |
P136724
|
FINISHED |
| Object | Airdrie, North Lanarkshire, Scotland |
—
|
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: Airdrie, North Lanarkshire, Scotland | Statement: [The Diamonds, clubHomeStadiumLocation, Airdrie, North Lanarkshire, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubHomeStadiumLocation Context triple: [The Diamonds, clubHomeStadiumLocation, Airdrie, North Lanarkshire, Scotland]
-
A.
homeStadiumLocatedIn
chosen
Indicates that the home stadium of a sports team or organization is geographically situated within a specified location or region.
-
B.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
C.
homeStadiumAlsoKnownAs
Indicates that an alternative or alias name is used for a stadium that serves as a team's home venue.
-
D.
leagueVenue
Indicates that a particular venue is used as the location where a league holds its games or events.
-
E.
cityOfHomeStadium
Indicates the city in which a given home stadium is located.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfd746481908fead735f9ccd021 |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:52 p.m.