Triple
T37093050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-111 |
E918477
|
entity |
| Predicate | issExpeditionReturned |
P169371
|
FINISHED |
| Object | Expedition 4 crew |
—
|
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 4 crew | Statement: [STS-111, issExpeditionReturned, Expedition 4 crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issExpeditionReturned Context triple: [STS-111, issExpeditionReturned, Expedition 4 crew]
-
A.
expeditionReturned
chosen
Indicates that an expedition has come back to its point of origin after completing its journey or mission.
-
B.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
C.
expeditionDelivered
Indicates that an expedition has successfully transported and handed over its intended items or results to the designated recipient or destination.
-
D.
expeditionReturnCountry
Indicates the country to which an expedition returns at the end of its journey.
-
E.
usedExpedition
Indicates that an entity employed or relied on a particular expedition (journey, mission, or exploratory campaign) to achieve some purpose or outcome.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.