Triple
T19804780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assiah |
E475780
|
entity |
| Predicate | isRealmWhere |
P48425
|
FINISHED |
| Object | divine energy becomes fully concretized |
—
|
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: divine energy becomes fully concretized | Statement: [Assiah, isRealmWhere, divine energy becomes fully concretized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRealmWhere Context triple: [Assiah, isRealmWhere, divine energy becomes fully concretized]
-
A.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
B.
residesInRealm
Indicates that an entity lives or exists within a particular realm or domain.
-
C.
currentRealm
Indicates the realm, domain, or context in which an entity presently exists or operates.
-
D.
hasSubrealm
Indicates that one realm or domain is a subordinate or contained sub-part of another, higher-level realm or domain.
-
E.
associatedWithRealm
chosen
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65427546c819082c8eb0d63e3f5fe |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.