Triple
T12665434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 3 |
E302540
|
entity |
| Predicate | actualTrajectory |
P12575
|
FINISHED |
| Object | high-altitude suborbital 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: high-altitude suborbital trajectory | Statement: [Pioneer 3, actualTrajectory, high-altitude suborbital trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualTrajectory Context triple: [Pioneer 3, actualTrajectory, high-altitude suborbital trajectory]
-
A.
trajectoryCoverage
Indicates the extent to which a path or trajectory spans, visits, or accounts for the relevant space, time, or set of target points.
-
B.
trajectoryType
chosen
Indicates the kind or pattern of motion an entity follows along its path over time.
-
C.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
D.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
E.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617e030881908444743b8a7e0d75 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.