Triple
T25638671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyke |
E642774
|
entity |
| Predicate | groupInclinationRange |
P133654
|
FINISHED |
| Object | about 164 to 166 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: about 164 to 166 degrees | Statement: [Kalyke, groupInclinationRange, about 164 to 166 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupInclinationRange Context triple: [Kalyke, groupInclinationRange, about 164 to 166 degrees]
-
A.
slopeAngleRange
Indicates the range of possible or allowed slope angles associated with a given entity or context.
-
B.
inclinationClass
Indicates a categorization of something based on the type or degree of its inclination or tilt.
-
C.
inclinationAngle
chosen
Indicates the angle at which one object or reference frame is tilted or inclined relative to another specified baseline or plane.
-
D.
gradeRangeContext
Indicates the range or span of grades within which a particular condition, evaluation, or context applies.
-
E.
lowerInclinationAngle
Indicates that one entity has a smaller or more downward-tilted inclination angle compared to another entity.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:38 p.m.