Triple
T21312805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-91 |
E525384
|
entity |
| Predicate | deliveredToMir |
P1386
|
FINISHED |
| Object | supplies and experiments |
—
|
LITERAL FINISHED |
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: supplies and experiments | Statement: [STS-91, deliveredToMir, supplies and experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveredToMir Context triple: [STS-91, deliveredToMir, supplies and experiments]
-
A.
deliveredIntoHandsOf
Indicates that something is physically transferred or formally handed over into the possession or control of a specified recipient.
-
B.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
C.
delivered
chosen
Indicates that something has been brought or transported to a recipient or destination, typically completing a transfer or fulfillment of an order, message, or service.
-
D.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
-
E.
designedToBeDeliveredBy
Indicates that one entity is intentionally created or configured so that it will be transported, distributed, or handed over by another specified entity.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcb45f08190a9bcaa366964a2cb |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:25 p.m.