Triple
T18497690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz T-15 |
E451990
|
entity |
| Predicate | redockingWithMirDate |
P37018
|
FINISHED |
| Object | 1986-06-25 |
—
|
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-06-25 | Statement: [Soyuz T-15, redockingWithMirDate, 1986-06-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redockingWithMirDate Context triple: [Soyuz T-15, redockingWithMirDate, 1986-06-25]
-
A.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
-
B.
dockingDate
chosen
Indicates the date on which one entity physically docks with or is scheduled to dock with another (e.g., a vehicle, vessel, or spacecraft).
-
C.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
D.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
E.
realignedOn
Indicates that something has been adjusted or repositioned so that it is now aligned with a specified reference or standard.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c15dec8190941e7c7a4cdebb66 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.