Triple
T11119613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalyaan |
E262980
|
entity |
| Predicate | apoapsisType |
P97654
|
FINISHED |
| Object | highly elliptical orbit |
—
|
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: highly elliptical orbit | Statement: [Mangalyaan, apoapsisType, highly elliptical orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apoapsisType Context triple: [Mangalyaan, apoapsisType, highly elliptical orbit]
-
A.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
B.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
C.
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.
-
D.
apogeeDistance_km
Indicates the distance in kilometers between an orbiting object and the central body at the farthest point (apogee) of its orbit.
-
E.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
- F. None of above. chosen
Provenance (4 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af7b72c8190a19dbcbb3a69fb5b |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d75112eb1c8190ba1dd51e42e8a7e8 |
completed | April 9, 2026, 7:11 a.m. |
Created at: April 8, 2026, 9:28 p.m.