Triple
T25869506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcana Coelestia |
E651712
|
entity |
| Predicate | coversChapters |
P6720
|
FINISHED |
| Object | Genesis 1–50 |
—
|
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: Genesis 1–50 | Statement: [Arcana Coelestia, coversChapters, Genesis 1–50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversChapters Context triple: [Arcana Coelestia, coversChapters, Genesis 1–50]
-
A.
containsChapter
chosen
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
C.
supportsChapters
Indicates that one entity provides assistance, resources, or endorsement to help establish, maintain, or strengthen chapters of another entity.
-
D.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
E.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 8:08 a.m.