Triple
T29998604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Launch program |
E762098
|
entity |
| Predicate | restructuringCompletionDate |
P168732
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Sea Launch program, restructuringCompletionDate, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restructuringCompletionDate Context triple: [Sea Launch program, restructuringCompletionDate, 2010]
-
A.
cuttingCompletionDate
Indicates the date on which a cutting process or operation is completed.
-
B.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
C.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
D.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
-
E.
refurbishmentPlannedCompletion
Indicates the scheduled date or time by which a refurbishment activity is planned to be completed.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:40 p.m.