Triple
T24323610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League Final 2020 |
E613035
|
entity |
| Predicate | notablePlayerBayern |
P9730
|
FINISHED |
| Object | Manuel Neuer |
—
|
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: Manuel Neuer | Statement: [UEFA Champions League Final 2020, notablePlayerBayern, Manuel Neuer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerBayern Context triple: [UEFA Champions League Final 2020, notablePlayerBayern, Manuel Neuer]
-
A.
BayernMunichCaptain
Indicates that the subject serves as the team captain of Bayern Munich.
-
B.
organNotablePlayer
Indicates that a person is a notable or distinguished player of a particular organ.
-
C.
notableGoalScorer
Indicates that the subject is recognized for having scored a significant or noteworthy number of goals, typically in a sports context.
-
D.
hasNotablePlayer
chosen
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
E.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ae127881909ef1772278181ce3 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:53 a.m.