Triple
T9808485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solar X-ray Monitor |
E238210
|
entity |
| Predicate | platformOrbitType |
P7214
|
FINISHED |
| Object | 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: lunar orbit | Statement: [Solar X-ray Monitor, platformOrbitType, lunar orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformOrbitType Context triple: [Solar X-ray Monitor, platformOrbitType, lunar orbit]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
supportsOrbitRegimes
Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
-
C.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
D.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
E.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb21ef32c8190ab4b09d157798451 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.