Triple
T11146037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C11 |
E263671
|
entity |
| Predicate | insertionOrbitApogeeApproximate |
P90087
|
FINISHED |
| Object | 22860 km |
—
|
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: 22860 km | Statement: [PSLV-C11, insertionOrbitApogeeApproximate, 22860 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insertionOrbitApogeeApproximate Context triple: [PSLV-C11, insertionOrbitApogeeApproximate, 22860 km]
-
A.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
B.
apoapsisType
Indicates the specific kind or classification of an orbit’s apoapsis (farthest point from the central body) associated with an entity.
-
C.
apoapsisBody
Indicates the celestial body that an orbiting object is farthest from at its apoapsis.
-
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.
apogeeDistance_km
chosen
Indicates the distance in kilometers between an orbiting object and the central body at the farthest point (apogee) of its orbit.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.