Triple
T38057287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA World Cup matches |
E950238
|
entity |
| Predicate | haveObjective |
P189916
|
FINISHED |
| Object | determine progression in 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: determine progression in FIFA World Cup | Statement: [FIFA World Cup matches, haveObjective, determine progression in FIFA World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveObjective Context triple: [FIFA World Cup matches, haveObjective, determine progression in FIFA World Cup]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
hasSocialObjective
Indicates that an entity is associated with or pursues a specific social goal or purpose as part of its activities or mission.
-
C.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
D.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
E.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:21 p.m.