Triple
T1319383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football Alliance |
E28180
|
entity |
| Predicate | roleRelativeToFootballLeague |
P14030
|
FINISHED |
| Object | rival league |
—
|
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: rival league | Statement: [Football Alliance, roleRelativeToFootballLeague, rival league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleRelativeToFootballLeague Context triple: [Football Alliance, roleRelativeToFootballLeague, rival league]
-
A.
roleAtSportsTeam
Indicates the specific position or function an individual holds within a sports team.
-
B.
roleInLeagueHistory
chosen
Indicates the specific function, contribution, or significance an entity has had within the historical development or narrative of a league.
-
C.
roleInCONCACAF
Indicates that one entity holds a specific role, position, or function within the CONCACAF organization or its activities.
-
D.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
E.
managerOfYearLeague
Indicates that an individual has been recognized as the manager of the year for a particular league in a given season or time period.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1780be8819083a9365b8a49305d |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.