Triple
T31793200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing Commercial Crew program |
E811523
|
entity |
| Predicate | contractAwardYear |
P75496
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Boeing Commercial Crew program, contractAwardYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractAwardYear Context triple: [Boeing Commercial Crew program, contractAwardYear, 2014]
-
A.
finalContractAwardYear
chosen
Indicates the calendar year in which the contract was ultimately and officially awarded.
-
B.
agreementYear
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
C.
workAwardYear
Indicates the year in which a particular work received a specific award.
-
D.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
-
E.
contractStartYear
Indicates the calendar year in which a contract between parties 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 30, 2026, 11:39 p.m.