Triple
T38044803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom Space |
E949587
|
entity |
| Predicate | AxiomStationPlannedOrbit |
P124080
|
FINISHED |
| Object | low Earth orbit |
—
|
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: low Earth orbit | Statement: [Axiom Space, AxiomStationPlannedOrbit, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AxiomStationPlannedOrbit Context triple: [Axiom Space, AxiomStationPlannedOrbit, low Earth orbit]
-
A.
originalPlannedOrbit
chosen
Indicates the initially intended or designed orbital path or parameters for an object before any changes or deviations occurred.
-
B.
spaceStationOrbit
Indicates that a space station is in orbit around a specified celestial body or location.
-
C.
isOrbitalRouteFor
Indicates that one path or trajectory serves as the designated orbital route followed by another object (such as a spacecraft or satellite).
-
D.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
E.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.