Triple
T1734155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Space Climate Observatory |
E37882
|
entity |
| Predicate | locationInSpace |
P9990
|
FINISHED |
| Object | halo orbit around Sun–Earth L1 |
—
|
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: halo orbit around Sun–Earth L1 | Statement: [Deep Space Climate Observatory, locationInSpace, halo orbit around Sun–Earth L1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInSpace Context triple: [Deep Space Climate Observatory, locationInSpace, halo orbit around Sun–Earth L1]
-
A.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
C.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
D.
locationOfVision
Indicates the place or setting where a vision or visual experience occurs or is perceived.
-
E.
spaceStationReentryLocation
Indicates the geographic location where a space station (or its remnants) reenters the Earth's atmosphere.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.