Triple
T35240845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Jackson |
E1017508
|
entity |
| Predicate | activeInLeagueAsManager |
P49850
|
FINISHED |
| Object | English 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: English football league system | Statement: [Mark Jackson, activeInLeagueAsManager, English football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInLeagueAsManager Context triple: [Mark Jackson, activeInLeagueAsManager, English football league system]
-
A.
managedInLeague
Indicates that an entity served as a manager or head coach for a team participating in a specified league.
-
B.
workedInLeagueAsManager
chosen
Indicates that a person has held a managerial role within a specific sports league.
-
C.
activeInLeague
Indicates that an entity (such as a team or player) is currently participating in or belongs to a particular league.
-
D.
tournamentParticipationAsManager
Indicates that an entity serves in the role of manager for a participant (such as a team or individual) in a specific tournament.
-
E.
activeAsManager
Indicates that an entity currently holds and performs the role or responsibilities of a manager in relation to another 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.