Triple
T32060695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Soul universe) |
E818738
|
entity |
| Predicate | coexistsWithRealm |
P56284
|
FINISHED |
| Object | The Great Before |
—
|
NE NERFINISHED |
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: The Great Before | Statement: [Earth (Soul universe), coexistsWithRealm, The Great Before]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coexistsWithRealm Context triple: [Earth (Soul universe), coexistsWithRealm, The Great Before]
-
A.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
B.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
C.
residesInRealm
Indicates that an entity lives or exists within a particular realm or domain.
-
D.
canCoexistWith
chosen
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
E.
oppositeRealmType
Indicates that two realms are of contrasting or mutually opposing types within a given classification or system.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f5356c8190848a6ecf234db9da |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:21 a.m.