Triple
T812352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish League Cup |
E17572
|
entity |
| Predicate | eligibleTeams |
P19216
|
FINISHED |
| Object | clubs from the Scottish 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: clubs from the Scottish league system | Statement: [Scottish League Cup, eligibleTeams, clubs from the Scottish league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleTeams Context triple: [Scottish League Cup, eligibleTeams, clubs from the Scottish league system]
-
A.
teamEligibility
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
B.
eligibleClubs
chosen
Indicates that certain clubs meet the required criteria or conditions to qualify for a specified status, activity, or benefit.
-
C.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
D.
byeTeamsPerConference
Indicates the number of teams in each conference that receive a bye (i.e., skip a round) in a competition or playoff structure.
-
E.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab4c7418819085cb64c6bf5fa70c |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa73df08819096d0553a4b2509de |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.