Triple
T8948151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friendship 7 |
E213273
|
entity |
| Predicate | orbitApogeeApprox |
P18900
|
FINISHED |
| Object | about 265 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 265 kilometers | Statement: [Friendship 7, orbitApogeeApprox, about 265 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitApogeeApprox Context triple: [Friendship 7, orbitApogeeApprox, about 265 kilometers]
-
A.
orbitApogee
chosen
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
B.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
C.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
-
D.
orbitFirstReached
Indicates the point in time or event when an object first successfully enters into a specified orbit.
-
E.
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.
- 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.