Triple
T34216774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutherglen Glencairn F.C. |
E877812
|
entity |
| Predicate | wonWestRegionSuperLeagueFirstDivisionIn |
P24503
|
FINISHED |
| Object | 2008–09 |
—
|
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: 2008–09 | Statement: [Rutherglen Glencairn F.C., wonWestRegionSuperLeagueFirstDivisionIn, 2008–09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonWestRegionSuperLeagueFirstDivisionIn Context triple: [Rutherglen Glencairn F.C., wonWestRegionSuperLeagueFirstDivisionIn, 2008–09]
-
A.
winnerLeagueDivision
chosen
Indicates that an entity has won a specific league division in a competitive context.
-
B.
wonEasternLeagueChampionship
Indicates that an entity secured the championship title in the Eastern League for a given season or competition.
-
C.
NationalLeagueWinner
Indicates that an entity is the team that won the championship title of the National League in a given season or year.
-
D.
firstWinnerLeague
Indicates that an entity is the team or participant that won a particular league competition for the first time.
-
E.
wonLeagueCup
Indicates that a team or competitor achieved victory in a specific league cup competition or tournament.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107e66e88190a799e0c78f1af117 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.