Triple
T28004025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Brigade |
E707224
|
entity |
| Predicate | supportsTeamInCompetition |
P6593
|
FINISHED |
| Object | Scottish Premiership |
—
|
NE NERFINISHED |
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 Premiership | Statement: [Green Brigade, supportsTeamInCompetition, Scottish Premiership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTeamInCompetition Context triple: [Green Brigade, supportsTeamInCompetition, Scottish Premiership]
-
A.
supportsCompetition
Indicates that one entity actively promotes, enables, or upholds the existence or functioning of competition involving another entity.
-
B.
supportsTeam
chosen
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
C.
supportsCompetitionParticipationOf
Indicates that one entity provides assistance, resources, or endorsement enabling another entity to take part in a competition.
-
D.
supportsTeamIdentity
Indicates that one entity contributes to establishing, reinforcing, or maintaining the shared identity of a team.
-
E.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: April 27, 2026, 7:59 p.m.