Triple
T29290099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain vs Morocco (2018 FIFA World Cup Group B) |
E742636
|
entity |
| Predicate | firstGoalType |
P72446
|
FINISHED |
| Object | one-on-one after defensive error |
—
|
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: one-on-one after defensive error | Statement: [Spain vs Morocco (2018 FIFA World Cup Group B), firstGoalType, one-on-one after defensive error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGoalType Context triple: [Spain vs Morocco (2018 FIFA World Cup Group B), firstGoalType, one-on-one after defensive error]
-
A.
goalType
chosen
Indicates the specific category or nature of a goal associated with an entity or action.
-
B.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
C.
debutGoalType
Indicates the type or category of goal scored in an entity’s debut appearance.
-
D.
directGoalType
Indicates that one entity serves as the immediate or primary goal type that another entity is directly aiming to achieve or realize.
-
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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: April 28, 2026, 1:01 p.m.