Triple
T11871358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Resupply Services |
E282413
|
entity |
| Predicate | firstOperationalMissionYear |
P13819
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Commercial Resupply Services, firstOperationalMissionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperationalMissionYear Context triple: [Commercial Resupply Services, firstOperationalMissionYear, 2012]
-
A.
firstOperationalCrewFlightYear
Indicates the year in which the first operational crewed flight associated with the subject took place.
-
B.
firstOperationalCargoMissionDate
Indicates the calendar date on which an entity conducted its first operational mission carrying cargo.
-
C.
firstOperationalUse
chosen
Indicates the point in time or context when something is used operationally for the very first time.
-
D.
firstCrewedTestFlightYear
Indicates the calendar year in which an entity conducted its first test flight involving a human crew.
-
E.
firstFlagshipLaunchYear
Indicates the calendar year in which an entity’s first flagship (primary or leading) product, service, or initiative was launched.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:43 p.m.