Triple
T4065451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExoMars programme |
E86312
|
entity |
| Predicate | launchYearPlanned |
P14322
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [ExoMars programme, launchYearPlanned, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchYearPlanned Context triple: [ExoMars programme, launchYearPlanned, 2016]
-
A.
originalPlannedLaunchYear
chosen
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
-
B.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
C.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
D.
launchedEndYear
Indicates the calendar year in which a launch event or activity came to an end.
-
E.
seventhPlanStartYear
Indicates the calendar year in which the seventh plan in a sequence officially begins.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.