Triple
T23750410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henning Berg |
E586946
|
entity |
| Predicate | trophiesWonWithBlackburnRovers |
P119173
|
FINISHED |
| Object | Premier League |
—
|
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: Premier League | Statement: [Henning Berg, trophiesWonWithBlackburnRovers, Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophiesWonWithBlackburnRovers Context triple: [Henning Berg, trophiesWonWithBlackburnRovers, Premier League]
-
A.
trophyWonWithArsenal
Indicates that a trophy was won by a person or team while they were with Arsenal Football Club.
-
B.
trophyWonWith
chosen
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
-
C.
uniqueAchievementInPremierLeagueEra
Indicates that the subject has accomplished something in the Premier League era that no other entity has matched or replicated.
-
D.
wonLeagueCup
Indicates that a team or competitor achieved victory in a specific league cup competition or tournament.
-
E.
editionOfCompetitionWon
Indicates that an entity has won a specific edition or instance of a competition.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc1d4e8819099d3b4136f28f0c6 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.