Triple
T37997227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 62 |
E947991
|
entity |
| Predicate | beganWithUndockingOf |
P189955
|
FINISHED |
| Object | Soyuz MS-13 |
—
|
NE NERFINISHED |
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: Soyuz MS-13 | Statement: [Expedition 62, beganWithUndockingOf, Soyuz MS-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganWithUndockingOf Context triple: [Expedition 62, beganWithUndockingOf, Soyuz MS-13]
-
A.
endedWithUndockingOf
Indicates that an event or process concluded with the action of undocking (separation of docked entities).
-
B.
undockedFromMir
Indicates that one entity separated and disengaged from the Mir space station after having been docked to it.
-
C.
lastCrewedUndockingDate
Indicates the calendar date on which the most recent undocking event occurred that involved a crewed vehicle.
-
D.
undockingDate
Indicates the date on which one object or vehicle separates and moves away from another to which it was previously docked.
-
E.
firstSuccessfulDockingWith
Indicates that one entity is the first other entity with which the subject successfully completed a docking operation.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.