Triple
T33095983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-07M |
E846909
|
entity |
| Predicate | returnCrewForExpedition35 |
P184027
|
FINISHED |
| Object | Chris Hadfield |
—
|
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: Chris Hadfield | Statement: [Soyuz TMA-07M, returnCrewForExpedition35, Chris Hadfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnCrewForExpedition35 Context triple: [Soyuz TMA-07M, returnCrewForExpedition35, Chris Hadfield]
-
A.
visitingExpeditionCrew
Indicates a relationship where a crew is temporarily present at a location or facility as a visiting expedition team, rather than being part of the resident or primary crew.
-
B.
ISSExpedition
Indicates a specific long-duration mission or crew rotation period conducted aboard the International Space Station.
-
C.
ISSExpeditionCrewExchange
Indicates a changeover event where one crew departs and another arrives for an expedition aboard the International Space Station.
-
D.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
E.
missionCrewStations
Indicates that specific crew stations are assigned or associated with a particular mission.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:26 a.m.