Triple
T4046348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proton rocket |
E84074
|
entity |
| Predicate | orbitTypesServed |
P48448
|
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: [Proton rocket, orbitTypesServed, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitTypesServed Context triple: [Proton rocket, orbitTypesServed, low Earth orbit]
-
A.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
supportsOrbitRegimes
chosen
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
-
C.
orbitsServed
Indicates that a mission, vehicle, or service has operated for or provided coverage during a specified number of orbital revolutions around a celestial body.
-
D.
orbitCapability
Indicates that one entity has the ability or suitability to orbit around another entity.
-
E.
spaceStationServed
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb6135b481909d2be890a2140ff9 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.