Triple
T21026497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M88 |
E517953
|
entity |
| Predicate | inclinationToLineOfSight |
P133654
|
FINISHED |
| Object | highly inclined |
—
|
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: highly inclined | Statement: [M88, inclinationToLineOfSight, highly inclined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inclinationToLineOfSight Context triple: [M88, inclinationToLineOfSight, highly inclined]
-
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.
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.
-
C.
inclinationToEarthEquator
Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
-
D.
angleOfIncident
Indicates the angle at which one entity (such as a ray, line, or object) strikes or approaches the surface or boundary of another entity.
-
E.
inclinationToGalacticPlane
Indicates the angle between an object's orbital or rotational plane and the galactic 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.