Triple
T4959199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascella |
E111361
|
entity |
| Predicate | eclipticProximity |
P20370
|
FINISHED |
| Object | lies close to the ecliptic 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: lies close to the ecliptic plane | Statement: [Ascella, eclipticProximity, lies close to the ecliptic plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eclipticProximity Context triple: [Ascella, eclipticProximity, lies close to the ecliptic plane]
-
A.
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.
-
B.
eclipticCrossing
Indicates that one object's path crosses the ecliptic plane at a specific point or during a specific event.
-
C.
liesOnEcliptic
chosen
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
-
D.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
E.
perihelionDistance
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.