Triple
T15830086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEXTANT |
E383845
|
entity |
| Predicate | navigationOutput |
P119805
|
FINISHED |
| Object | spacecraft position |
—
|
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: spacecraft position | Statement: [SEXTANT, navigationOutput, spacecraft position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationOutput Context triple: [SEXTANT, navigationOutput, spacecraft position]
-
A.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
navigationEnvironment
Indicates the contextual conditions or surroundings in which navigation or movement from one place to another occurs.
-
D.
navigationProblemAddressed
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
E.
navigationKnowledge
Indicates that an entity possesses information or understanding related to navigating or determining routes within an environment or system.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e636bb48190a6b39feb550aaa3d |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.