Triple
T29290103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain vs Morocco (2018 FIFA World Cup Group B) |
E742636
|
entity |
| Predicate | secondMoroccoGoalMethod |
P180330
|
FINISHED |
| Object | header from corner |
—
|
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: header from corner | Statement: [Spain vs Morocco (2018 FIFA World Cup Group B), secondMoroccoGoalMethod, header from corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMoroccoGoalMethod Context triple: [Spain vs Morocco (2018 FIFA World Cup Group B), secondMoroccoGoalMethod, header from corner]
-
A.
secondMoroccoGoalScoredBy
Indicates the player who scored Morocco’s second goal in a given match.
-
B.
goalsByMorocco
Indicates the number of goals that were scored by Morocco.
-
C.
usedByMorocco
chosen
Indicates that something is utilized, employed, or operated by Morocco.
-
D.
moroccoEliminated
Indicates that Morocco has been removed from further participation or contention, typically by losing in a competitive context such as a tournament or qualification process.
-
E.
moroccoPreviousWorldCupMatch
Indicates that the referenced match immediately precedes another World Cup match played by Morocco in chronological order.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 1:01 p.m.