Triple
T37093049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-111 |
E918477
|
entity |
| Predicate | issExpeditionDelivered |
P168991
|
FINISHED |
| Object | Expedition 5 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 5 crew | Statement: [STS-111, issExpeditionDelivered, Expedition 5 crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issExpeditionDelivered Context triple: [STS-111, issExpeditionDelivered, Expedition 5 crew]
-
A.
expeditionDelivered
chosen
Indicates that an expedition has successfully transported and handed over its intended items or results to the designated recipient or destination.
-
B.
expeditionReturned
Indicates that an expedition has come back to its point of origin after completing its journey or mission.
-
C.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
D.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
E.
deliveredWith
Indicates that one item, service, or message is brought or transported to a recipient together with another, as part of the same delivery.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.