Triple
T759813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Professional Football League |
E16041
|
entity |
| Predicate | promotionRelegationSystem |
P2678
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Scottish Professional Football League, promotionRelegationSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionRelegationSystem Context triple: [Scottish Professional Football League, promotionRelegationSystem, yes]
-
A.
relegationSystem
chosen
Indicates a system in which entities are moved to a lower tier or level based on their performance or ranking within a structured hierarchy.
-
B.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
C.
runnerUpLeague
Indicates that an entity finished in second place in a league competition.
-
D.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
-
E.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a68158508190998da10e69252662 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.