Triple
T22270423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Grand Prix |
E550459
|
entity |
| Predicate | contractExtensionAnnounced |
P147628
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Mexican Grand Prix, contractExtensionAnnounced, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractExtensionAnnounced Context triple: [Mexican Grand Prix, contractExtensionAnnounced, 2022]
-
A.
claimedExtensionBy
Indicates that one entity asserts or designates another entity as its extension, add-on, or expansion.
-
B.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
-
C.
announcedClosure
Indicates that an entity has publicly declared the intention to shut down, discontinue, or close another entity or operation.
-
D.
announcedWith
Indicates that one entity was publicly revealed, declared, or introduced at the same time as, and in explicit association with, another entity.
-
E.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bf53a481909e2c79de4144f332 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.