Triple
T29290095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain vs Morocco (2018 FIFA World Cup Group B) |
E742636
|
entity |
| Predicate | lateEqualiserValidation |
P121839
|
FINISHED |
| Object | VAR |
—
|
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: VAR | Statement: [Spain vs Morocco (2018 FIFA World Cup Group B), lateEqualiserValidation, VAR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lateEqualiserValidation Context triple: [Spain vs Morocco (2018 FIFA World Cup Group B), lateEqualiserValidation, VAR]
-
A.
lateEqualiserType
Indicates that the type or nature of an equalising score is specifically classified as a “late” equaliser, occurring near the end of a match or game.
-
B.
equaliserType
Indicates that one entity specifies or classifies the type or category of equaliser associated with another entity.
-
C.
finalEqualiserScorer
Indicates that the subject is the player who scored the final goal that brought the scores level in a match.
-
D.
requiresValidationAt
chosen
Indicates that an entity must undergo validation at a specific point, condition, or stage in a process.
-
E.
equoIs
Indicates that two entities are considered equal or equivalent in the given context.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 1:01 p.m.