Triple
T36016810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book IV (De Astronomica) |
E1041863
|
entity |
| Predicate | hasAstronomicalContent |
P62338
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Book IV (De Astronomica), hasAstronomicalContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstronomicalContent Context triple: [Book IV (De Astronomica), hasAstronomicalContent, yes]
-
A.
isLinkedToAstronomy
chosen
Indicates that something has a connection or relevant association to the field or study of astronomy.
-
B.
containsAstronomicalEvent
Indicates that a location, region, or time period includes or encompasses a specific astronomical event within its bounds or duration.
-
C.
isAstronomicalObject
Indicates that something is classified as an astronomical object, such as a star, planet, moon, asteroid, or similar celestial body.
-
D.
DeAstronomicaIs
Indicates that something is identified as or classified as "De Astronomica" (e.g., belonging to or being the work/text known as De Astronomica).
-
E.
astronomicalContext
Indicates the astronomical setting or frame of reference within which an object, event, or observation is situated or interpreted.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:07 p.m.