Triple
T2849415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis III |
E63055
|
entity |
| Predicate | returnSegment |
P43403
|
FINISHED |
| Object | Orion to Earth |
—
|
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: Orion to Earth | Statement: [Artemis III, returnSegment, Orion to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnSegment Context triple: [Artemis III, returnSegment, Orion to Earth]
-
A.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
B.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
C.
openedSegment
Indicates that one entity has initiated or created a new segment, section, or interval within another entity or process.
-
D.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
E.
returnBasis
Indicates the basis, method, or terms under which something is returned (e.g., goods, funds, or data) from one party or context to another.
- F. None of above. chosen
Provenance (4 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.