Triple
T2129916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Over-Soul |
E46513
|
entity |
| Predicate | unites |
P35330
|
FINISHED |
| Object | all individual souls |
—
|
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: all individual souls | Statement: [the Over-Soul, unites, all individual souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unites Context triple: [the Over-Soul, unites, all individual souls]
-
A.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
B.
politicalUnion
Indicates a formal relationship in which two or more political entities are joined under a shared governance or institutional framework.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
E.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
- F. None of above. chosen
Provenance (4 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb77ccc4819087bee5dbb91b5ae8 |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb895d11881908345032595a679ba |
completed | March 7, 2026, 5:33 a.m. |
Created at: March 4, 2026, 7:44 p.m.