Triple
T37360878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands 2014 World Cup campaign |
E927572
|
entity |
| Predicate | backupGoalkeeper |
P187774
|
FINISHED |
| Object | Tim Krul |
—
|
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: Tim Krul | Statement: [Netherlands 2014 World Cup campaign, backupGoalkeeper, Tim Krul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupGoalkeeper Context triple: [Netherlands 2014 World Cup campaign, backupGoalkeeper, Tim Krul]
-
A.
goalkeeperAction
Indicates actions performed by a goalkeeper in the context of defending the goal, such as saving, catching, blocking, or distributing the ball.
-
B.
substituteGoalkeeper
Indicates that one goalkeeper is replaced by another goalkeeper during a match.
-
C.
goaltender
Indicates a relationship where an entity serves as the goalkeeper or primary defender of the goal for a team in a game or sport.
-
D.
bestGoalkeeper
Indicates that the subject is considered the top-performing or most skilled goalkeeper among a specified group or context.
-
E.
losingGoaltender
Indicates that a particular goaltender is the one who was in net for the team that lost the game.
- F. None of above. chosen
Provenance (4 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.