Triple
T35665849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medium Earth orbit |
E1030560
|
entity |
| Predicate | hostsConstellation |
P70866
|
FINISHED |
| Object | GPS |
—
|
NE NERFINISHED |
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: GPS | Statement: [Medium Earth orbit, hostsConstellation, GPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsConstellation Context triple: [Medium Earth orbit, hostsConstellation, GPS]
-
A.
hostConstellation
Indicates the constellation in which an astronomical object is located or that is considered to host it.
-
B.
hostGalaxyConstellation
Indicates the constellation in which the host galaxy of an object is located.
-
C.
parentConstellation
Indicates that one constellation is the larger or primary constellation within which another constellation is contained or of which it is a part.
-
D.
usesConstellation
chosen
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
E.
hostStarCatalog
Indicates that a celestial object’s host star is listed or identified within a specific astronomical catalog.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fac9a748190bbead51a19556c63 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.