Triple
T8948150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friendship 7 |
E213273
|
entity |
| Predicate | orbitPerigeeApprox |
P26358
|
FINISHED |
| Object | about 159 kilometers |
—
|
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: about 159 kilometers | Statement: [Friendship 7, orbitPerigeeApprox, about 159 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitPerigeeApprox Context triple: [Friendship 7, orbitPerigeeApprox, about 159 kilometers]
-
A.
perigee
chosen
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
B.
perihelionDistance
Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
-
C.
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.
-
D.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
E.
orbitFirstReached
Indicates the point in time or event when an object first successfully enters into a specified 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6709c7a48190ab503083a1d6a29f |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.