Triple
T20946159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphere of Jupiter |
E515847
|
entity |
| Predicate | levelOfBeatitude |
P60422
|
FINISHED |
| Object | high but not ultimate |
—
|
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: high but not ultimate | Statement: [Sphere of Jupiter, levelOfBeatitude, high but not ultimate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelOfBeatitude Context triple: [Sphere of Jupiter, levelOfBeatitude, high but not ultimate]
-
A.
containsBeatitude
Indicates that one entity includes or embodies a state of blessedness, spiritual happiness, or divine favor in relation to another.
-
B.
levelInSoul
chosen
Indicates a relationship where an entity has a specific level, rank, or degree within a soul or soul-related state.
-
C.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
D.
blessedWith
Indicates that one entity has received a positive gift, talent, quality, or advantage attributed to another source.
-
E.
worshipLevel
Indicates the degree or intensity to which one entity reveres, honors, or performs acts of worship toward 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad7f67481908675e76736f5e0c3 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:56 p.m.