Triple
T17725522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-310 sounding rocket |
E442450
|
entity |
| Predicate | typicalApogee |
P52280
|
FINISHED |
| Object | approximately 150 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: approximately 150 kilometers | Statement: [S-310 sounding rocket, typicalApogee, approximately 150 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApogee Context triple: [S-310 sounding rocket, typicalApogee, approximately 150 kilometers]
-
A.
apogeeUnit
Indicates the unit of measurement used to express the apogee (maximum distance or height) of an object’s trajectory or orbit.
-
B.
apogeeCapability
chosen
Indicates the maximum altitude or apogee that an entity is capable of reaching or supporting.
-
C.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalStar
Indicates that an entity is a representative or characteristic example of stars in general, exhibiting the usual or expected properties of stars.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47489c59c8190bbffefad20dc6346 |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.