Triple
T11146036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C11 |
E263671
|
entity |
| Predicate | insertionOrbitPerigeeApproximate |
P26358
|
FINISHED |
| Object | 255 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: 255 km | Statement: [PSLV-C11, insertionOrbitPerigeeApproximate, 255 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insertionOrbitPerigeeApproximate Context triple: [PSLV-C11, insertionOrbitPerigeeApproximate, 255 km]
-
A.
perigee
chosen
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
B.
orbitFirstReached
Indicates the point in time or event when an object first successfully enters into a specified orbit.
-
C.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
-
D.
minimumOrbitIntersectionDistanceWithEarth_au
Indicates the smallest distance, measured in astronomical units, between an object's orbit and Earth's orbit at their closest point of approach.
-
E.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
- 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.