Triple
T20016687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killie |
E494737
|
entity |
| Predicate | playsHomeLeague |
P3751
|
FINISHED |
| Object | top tiers of Scottish football |
—
|
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: top tiers of Scottish football | Statement: [Killie, playsHomeLeague, top tiers of Scottish football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsHomeLeague Context triple: [Killie, playsHomeLeague, top tiers of Scottish football]
-
A.
playsSelectHomeGamesAt
Indicates that an entity (typically a sports team) holds some or all of its designated home games at a specified venue or location.
-
B.
homeLeague
chosen
Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
-
C.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
D.
homeLeagueOf
Indicates that a league is the primary or official league in which a team or club regularly competes.
-
E.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623cb8188190b95913ffed895930 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.