Triple
T36494057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-102 |
E899129
|
entity |
| Predicate | ISSExpeditionCrewDelivered |
P126722
|
FINISHED |
| Object | Expedition 2 |
—
|
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 2 | Statement: [STS-102, ISSExpeditionCrewDelivered, Expedition 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISSExpeditionCrewDelivered Context triple: [STS-102, ISSExpeditionCrewDelivered, Expedition 2]
-
A.
ISSExpeditionCrewExchange
Indicates a changeover event where one crew departs and another arrives for an expedition aboard the International Space Station.
-
B.
ISSExpedition
Indicates a specific long-duration mission or crew rotation period conducted aboard the International Space Station.
-
C.
broughtToISS
chosen
Indicates that an object or entity was transported or delivered to the International Space Station (ISS).
-
D.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
E.
spaceStationDelivered
Indicates that a space station has been successfully transported and delivered to its intended location or recipient.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.