Triple
T10048539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermes spacecraft |
E207678
|
entity |
| Predicate | travelRoute |
P79601
|
FINISHED |
| Object | Earth–Mars transfer orbit |
—
|
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: Earth–Mars transfer orbit | Statement: [Hermes spacecraft, travelRoute, Earth–Mars transfer orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelRoute Context triple: [Hermes spacecraft, travelRoute, Earth–Mars transfer orbit]
-
A.
travelRouteOf
chosen
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
B.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
C.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
D.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf8cf4f0819084d831e1986790be |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.