Triple
T10058561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle |
E208923
|
entity |
| Predicate | typicalInclinationRange |
P8549
|
FINISHED |
| Object | 28.5 degrees to 57 degrees |
—
|
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: 28.5 degrees to 57 degrees | Statement: [Space Shuttle, typicalInclinationRange, 28.5 degrees to 57 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInclinationRange Context triple: [Space Shuttle, typicalInclinationRange, 28.5 degrees to 57 degrees]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
lowerInclinationAngle
Indicates that one entity has a smaller or more downward-tilted inclination angle compared to another entity.
-
C.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
D.
orbitInclinationRange
chosen
Indicates the range of possible orbital inclination angles within which an object’s orbit is oriented relative to a reference plane.
-
E.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfb0f17c8190a8c0cfb02863537d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.