Triple
T19549048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulysses |
E489150
|
entity |
| Predicate | trajectoryAssist |
P136542
|
FINISHED |
| Object | Jupiter gravity assist |
—
|
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: Jupiter gravity assist | Statement: [Ulysses, trajectoryAssist, Jupiter gravity assist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trajectoryAssist Context triple: [Ulysses, trajectoryAssist, Jupiter gravity assist]
-
A.
trajectoryType
Indicates the kind or pattern of motion an entity follows along its path over time.
-
B.
trailBehavior
Indicates how an entity behaves, moves, or leaves traces along a path or trajectory over time.
-
C.
trajectoryCoverage
Indicates the extent to which a path or trajectory spans, visits, or accounts for the relevant space, time, or set of target points.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
trajectoryExpansion
Indicates how the path or course of something spreads, widens, or diversifies over time or space.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2f39188190976e8b6b111499a0 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:41 p.m.