Triple
T26529574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crew-2 |
E670781
|
entity |
| Predicate | issExpeditionParticipation |
P119962
|
FINISHED |
| Object | Expedition 65 |
—
|
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: Expedition 65 | Statement: [Crew-2, issExpeditionParticipation, Expedition 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issExpeditionParticipation Context triple: [Crew-2, issExpeditionParticipation, Expedition 65]
-
A.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
B.
issExpeditionRotation
Indicates that a given time period or event corresponds to a specific rotation (crew increment) of an International Space Station expedition.
-
C.
journeyParticipation
chosen
Indicates that an entity takes part in, accompanies, or is otherwise involved in a specific journey or trip.
-
D.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
E.
issExpeditionCrewExchange
Indicates that an event involves the exchange or rotation of crew members on the International Space Station (ISS) between different expeditions.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.