Triple
T3514017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Satellite Control Network |
E74262
|
entity |
| Predicate | supportsOrbitRegimes |
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: [Air Force Satellite Control Network, supportsOrbitRegimes, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOrbitRegimes Context triple: [Air Force Satellite Control Network, supportsOrbitRegimes, 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.
orbitCapability
Indicates that one entity has the ability or suitability to orbit around another entity.
-
C.
numberOfOrbitalPlanes
Indicates the specific count of distinct orbital planes associated with an object or system.
-
D.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
E.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc2efa4c8190ac1ca221f3f0eba4 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.