Triple
T25638933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinope |
E642780
|
entity |
| Predicate | apoapsisRelativeToJupiter |
P97653
|
FINISHED |
| Object | very large |
—
|
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: very large | Statement: [Sinope, apoapsisRelativeToJupiter, very large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apoapsisRelativeToJupiter Context triple: [Sinope, apoapsisRelativeToJupiter, very large]
-
A.
apoapsisBody
chosen
Indicates the celestial body that an orbiting object is farthest from at its apoapsis.
-
B.
apoapsisType
Indicates the specific kind or classification of an orbit’s apoapsis (farthest point from the central body) associated with an entity.
-
C.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
D.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
E.
relationToJupiter
Indicates a spatial or conceptual relationship that an entity has with the planet Jupiter, such as position, distance, or association relative to it.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:38 p.m.