Triple
T33095979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-07M |
E846909
|
entity |
| Predicate | associatedExpedition |
P59805
|
FINISHED |
| Object | Expedition 34 |
E846910
|
NE 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: Expedition 34 | Statement: [Soyuz TMA-07M, associatedExpedition, Expedition 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedExpedition Context triple: [Soyuz TMA-07M, associatedExpedition, Expedition 34]
-
A.
relatedExpedition
Indicates that one expedition has a connection or association with another expedition, such as being part of the same project, time period, or thematic context.
-
B.
involvedExpedition
Indicates participation of an entity in a specific expedition, such as taking part in or being associated with that exploratory journey or mission.
-
C.
usedByExpedition
Indicates that something (such as an object, resource, or method) is utilized or employed by an expedition in the course of its activities.
-
D.
followsExpeditionTo
Indicates that one entity accompanies or trails another entity on an expedition or journey to a particular destination.
-
E.
expeditionMemberOf
chosen
Indicates that an entity participates as a member in a specific expedition.
- F. None of above.
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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f02b316481909ba457919ef0d8c7 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.