Triple
T23679144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS-203 |
E584968
|
entity |
| Predicate | apogeeApprox |
P152963
|
FINISHED |
| Object | ~190 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: ~190 km | Statement: [AS-203, apogeeApprox, ~190 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apogeeApprox Context triple: [AS-203, apogeeApprox, ~190 km]
-
A.
apogeeLocation
Indicates the location in space where an orbiting object is at its farthest point (apogee) from the body it orbits.
-
B.
apogeeUnit
Indicates the unit of measurement used to express the apogee (maximum distance or height) of an object’s trajectory or orbit.
-
C.
apogeeCapability
Indicates the maximum altitude or apogee that an entity is capable of reaching or supporting.
-
D.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
E.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f5a7b48190b93d27416003e173 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.