Triple
T35949812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 EFL Championship |
E1039688
|
entity |
| Predicate | notableManagerTeam |
P207111
|
FINISHED |
| Object | Brentford F.C. |
E82417
|
NE 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: Brentford F.C. | Statement: [2020–21 EFL Championship, notableManagerTeam, Brentford F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableManagerTeam Context triple: [2020–21 EFL Championship, notableManagerTeam, Brentford F.C.]
-
A.
notableManagerInLeague
Indicates that a manager is recognized as notable or distinguished within a particular sports league.
-
B.
notableTeamLeader
Indicates that an entity serves as a prominent or distinguished leader of a particular team.
-
C.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
-
D.
NLManagerTeam
Indicates that an entity serves as the manager or head coach of a particular team.
-
E.
notableTeams
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
- F. None of above. chosen
Provenance (5 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b415a998819092a9ca9dfc366bf5 |
completed | June 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.