Triple
T27752811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-113 |
E701254
|
entity |
| Predicate | expeditionCrewRotation |
P124144
|
FINISHED |
| Object | Expedition 5 |
—
|
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 5 | Statement: [STS-113, expeditionCrewRotation, Expedition 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionCrewRotation Context triple: [STS-113, expeditionCrewRotation, Expedition 5]
-
A.
ISSExpeditionCrewExchange
Indicates a changeover event where one crew departs and another arrives for an expedition aboard the International Space Station.
-
B.
issExpeditionCrewExchange
chosen
Indicates that an event involves the exchange or rotation of crew members on the International Space Station (ISS) between different expeditions.
-
C.
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.
-
D.
usesCrewRotationWith
Indicates that one entity applies a crew rotation system or schedule in conjunction with another entity.
-
E.
crewExchange
Indicates a transfer or replacement of personnel between two crews or crewed entities.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63720253c819089ddbecbcbe6401a |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.