Triple
T27701980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldřich Nejedlý |
E698450
|
entity |
| Predicate | goalScoredInCompetition |
P162959
|
FINISHED |
| Object | 5 (1934 FIFA World Cup) |
—
|
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: 5 (1934 FIFA World Cup) | Statement: [Oldřich Nejedlý, goalScoredInCompetition, 5 (1934 FIFA World Cup)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalScoredInCompetition Context triple: [Oldřich Nejedlý, goalScoredInCompetition, 5 (1934 FIFA World Cup)]
-
A.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
B.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
C.
scoredGoalsInFinalOf
Indicates that one entity scored one or more goals in the final match of a specified competition or event.
-
D.
goalScorerIn
chosen
Indicates that an entity is the player who scored a goal in a particular match or event.
-
E.
winningGoalType
Indicates the specific manner or category of the goal that determined the final victory in a competition or match.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a398c08190995dd36a2e958b04 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:57 p.m.