Triple
T10048538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermes spacecraft |
E207678
|
entity |
| Predicate | maneuver |
P22224
|
FINISHED |
| Object | gravity assist around 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: gravity assist around Earth | Statement: [Hermes spacecraft, maneuver, gravity assist around Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maneuver Context triple: [Hermes spacecraft, maneuver, gravity assist around Earth]
-
A.
notableManeuver
chosen
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
B.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
C.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
mobilization
Indicates the process by which entities are organized, activated, or assembled to take coordinated action or move into a state of readiness.
- 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.