Triple
T427410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 10 |
E9637
|
entity |
| Predicate | trajectory |
P12575
|
FINISHED |
| Object | heliocentric escape trajectory |
—
|
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: heliocentric escape trajectory | Statement: [Pioneer 10, trajectory, heliocentric escape trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trajectory Context triple: [Pioneer 10, trajectory, heliocentric escape trajectory]
-
A.
trajectoryType
chosen
Indicates the kind or pattern of motion an entity follows along its path over time.
-
B.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
C.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
D.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
E.
tracesTo
Indicates a relationship where one item can be followed or linked back as the origin, source, or cause of another.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eed7f3508190995dcd39586ed614 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.