Triple
T36486410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon Impact Probe |
E898943
|
entity |
| Predicate | orbitFromWhichDeployed |
P171533
|
FINISHED |
| Object | 100 km circular lunar 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: 100 km circular lunar orbit | Statement: [Moon Impact Probe, orbitFromWhichDeployed, 100 km circular lunar orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitFromWhichDeployed Context triple: [Moon Impact Probe, orbitFromWhichDeployed, 100 km circular lunar orbit]
-
A.
deploymentOrbit
chosen
Indicates the orbital path or trajectory into which an object (typically a spacecraft or satellite) is placed at the time of its deployment.
-
B.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
C.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
D.
spacecraftOrigin
Indicates the place or source from which a spacecraft was originally launched, built, or sent.
-
E.
orbiterDesignation
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.