Triple
T21926531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epitome of the Almagest |
E541457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval astronomical treatise |
C28473
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval astronomical treatise Context triple: [Epitome of the Almagest, instanceOf, medieval astronomical treatise]
-
A.
astronomical chronicle
An astronomical chronicle is a systematic record of celestial events and observations, often organized by date, that documents phenomena such as planetary motions, eclipses, comets, and stellar occurrences over time.
-
B.
medieval scientific work
chosen
A medieval scientific work is a scholarly text produced between roughly the 5th and 15th centuries that investigates natural phenomena using the philosophical, religious, and observational frameworks of its time.
-
C.
medieval scientific tradition
A medieval scientific tradition is a historically rooted system of inquiry and knowledge transmission that blends classical learning, religious doctrine, and empirical observation within the intellectual, institutional, and cultural frameworks of the Middle Ages.
-
D.
Hindu astronomical work
A Hindu astronomical work is a traditional Indian text that systematically describes celestial bodies, their motions, and related mathematical and calendrical calculations within the framework of Hindu cosmology.
-
E.
work by Claudius Ptolemy
A work by Claudius Ptolemy is any written treatise, map, or astronomical, geographical, or mathematical text authored or attributed to the Greco-Roman scholar Claudius Ptolemy.
- F. None of above.
Provenance (1 batch)
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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:46 p.m.