Triple
T1443457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galilean moons |
E31124
|
entity |
| Predicate | haveOrbitalPlane |
P7296
|
FINISHED |
| Object | close to Jupiter equatorial plane |
—
|
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: close to Jupiter equatorial plane | Statement: [Galilean moons, haveOrbitalPlane, close to Jupiter equatorial plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveOrbitalPlane Context triple: [Galilean moons, haveOrbitalPlane, close to Jupiter equatorial plane]
-
A.
hasOrbitalPlane
chosen
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
B.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
C.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
D.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
E.
liesOnEcliptic
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.