Triple
T20972850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphere of Venus |
E516546
|
entity |
| Predicate | soulsContained |
P132141
|
FINISHED |
| Object | lovers illuminated by divine love |
—
|
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: lovers illuminated by divine love | Statement: [Sphere of Venus, soulsContained, lovers illuminated by divine love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soulsContained Context triple: [Sphere of Venus, soulsContained, lovers illuminated by divine love]
-
A.
receivesSoulsOf
Indicates that one entity takes in or accepts the souls of another entity or group of entities.
-
B.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
C.
sanctumContains
chosen
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
D.
hasWorldSoul
Indicates that an entity possesses or is intrinsically connected to a fundamental, unifying spiritual essence of a world or cosmos.
-
E.
levelInSoul
Indicates a relationship where an entity has a specific level, rank, or degree within a soul or soul-related state.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba161d88190b8905891f449004e |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:45 p.m.