Triple
T36565041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 4 |
E901953
|
entity |
| Predicate | crewTransferMethod |
P185865
|
FINISHED |
| Object | spacewalk |
—
|
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: spacewalk | Statement: [Soyuz 4, crewTransferMethod, spacewalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransferMethod Context triple: [Soyuz 4, crewTransferMethod, spacewalk]
-
A.
plannedCrewTransferMethod
Indicates the method or means by which a crew transfer is intended or scheduled to be carried out.
-
B.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
-
C.
transportedBetween
Indicates that an entity is moved or conveyed from one specified location or state to another.
-
D.
shipAction
Indicates an action involving the sending, transporting, or delivering of something from one party or location to another.
-
E.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.