Triple
T36484873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Systems/Loral |
E898908
|
entity |
| Predicate | focusesOnOrbitType |
P96574
|
FINISHED |
| Object | geostationary 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: geostationary orbit | Statement: [Space Systems/Loral, focusesOnOrbitType, geostationary orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnOrbitType Context triple: [Space Systems/Loral, focusesOnOrbitType, geostationary orbit]
-
A.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
designedForOrbitType
chosen
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
C.
associatedObjectOrbit
Indicates that one object’s orbit is linked to, derived from, or otherwise related to the orbit of another object.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
hasOrbit
Indicates that one entity follows a curved, typically gravitationally bound path around another 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:10 p.m.