Triple
T23679145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS-203 |
E584968
|
entity |
| Predicate | inclinationApprox |
P133654
|
FINISHED |
| Object | ~31.7 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: ~31.7 degrees | Statement: [AS-203, inclinationApprox, ~31.7 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inclinationApprox Context triple: [AS-203, inclinationApprox, ~31.7 degrees]
-
A.
inclinationAngle
chosen
Indicates the angle at which one object or reference frame is tilted or inclined relative to another specified baseline or plane.
-
B.
inclinationClass
Indicates a categorization of something based on the type or degree of its inclination or tilt.
-
C.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
-
D.
inclinationToEarthEquator
Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
-
E.
inclinationToEcliptic
Indicates the angle between an object's orbital plane and the plane of the ecliptic, describing how tilted its orbit is relative to Earth's orbital plane.
- 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_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. |
Created at: April 17, 2026, 6:51 p.m.