Triple
T23042726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2030 FIFA World Cup |
E573782
|
entity |
| Predicate | scheduledForYear |
P42174
|
FINISHED |
| Object | 2030 |
—
|
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: 2030 | Statement: [2030 FIFA World Cup, scheduledForYear, 2030]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledForYear Context triple: [2030 FIFA World Cup, scheduledForYear, 2030]
-
A.
scheduledInYear
chosen
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
B.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
C.
originallyScheduledYear
Indicates the year in which something was first planned or scheduled to occur, before any later changes or rescheduling.
-
D.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
E.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18516417081908bf747b20de23a75 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.