Triple
T36016809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book IV (De Astronomica) |
E1041863
|
entity |
| Predicate | hasMythologicalContent |
P137609
|
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), hasMythologicalContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalContent Context triple: [Book IV (De Astronomica), hasMythologicalContent, yes]
-
A.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
B.
mythologicalContent
chosen
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
hasMythologicalDomain
Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
-
D.
hasMythologicalBasis
Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
-
E.
hasMythologicalUsage
Indicates that something is used, referenced, or functions within a mythological context or tradition.
- 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_69f7ace0a35c819087293a87666b9f07 |
completed | May 3, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.