Triple
T16257628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAG |
E394670
|
entity |
| Predicate | hostSpacecraftOrbit |
P53925
|
FINISHED |
| Object | polar orbit around Venus |
—
|
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: polar orbit around Venus | Statement: [MAG, hostSpacecraftOrbit, polar orbit around Venus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSpacecraftOrbit Context triple: [MAG, hostSpacecraftOrbit, polar orbit around Venus]
-
A.
hostSpacecraft
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
B.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
C.
hostOrbit
Indicates that one celestial body orbits around another body that serves as its primary gravitational host.
-
D.
orbitReference
chosen
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
-
E.
spacePosition
Indicates the spatial location or coordinates of an entity within a defined space or reference frame.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459b1624819086bf681075097235 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.