Triple
T3049128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir program |
E83524
|
entity |
| Predicate | firstModuleLaunchDate |
P29648
|
FINISHED |
| Object | 1986-02-20 |
—
|
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: 1986-02-20 | Statement: [Mir program, firstModuleLaunchDate, 1986-02-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstModuleLaunchDate Context triple: [Mir program, firstModuleLaunchDate, 1986-02-20]
-
A.
firstModuleLaunch
chosen
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
B.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
C.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
D.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb00a348190877c9cbf0f13cba4 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.