Triple
T36486140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | enhanced Polar Outflow Probe |
E898936
|
entity |
| Predicate | inclinationType |
P111184
|
FINISHED |
| Object | high-inclination orbit |
—
|
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: high-inclination orbit | Statement: [enhanced Polar Outflow Probe, inclinationType, high-inclination orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inclinationType Context triple: [enhanced Polar Outflow Probe, inclinationType, high-inclination orbit]
-
A.
inclinationClass
chosen
Indicates a categorization of something based on the type or degree of its inclination or tilt.
-
B.
inclinationAngle
Indicates the angle at which one object or reference frame is tilted or inclined relative to another specified baseline or plane.
-
C.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
-
D.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
E.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.