Triple
T25863685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Stand |
E651552
|
entity |
| Predicate | clubServedLeagueSystem |
P158791
|
FINISHED |
| Object | Scottish football league system |
—
|
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: Scottish football league system | Statement: [West Stand, clubServedLeagueSystem, Scottish football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubServedLeagueSystem Context triple: [West Stand, clubServedLeagueSystem, Scottish football league system]
-
A.
supportedClubLeague
Indicates that an entity (typically a person or group) actively supported a particular sports club participating in a specified league.
-
B.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
C.
clubScope
Indicates that something is within the organizational, functional, or contextual scope of a particular club.
-
D.
homeClubLeagueSystem
chosen
Indicates that a club’s primary or home competition participation is within a specified league system.
-
E.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026ddccc8190a7d7cc460a5ede96 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:06 a.m.