Triple
T28667467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Gods |
E725621
|
entity |
| Predicate | existenceRealm |
P134555
|
FINISHED |
| Object | beyond conventional space |
—
|
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: beyond conventional space | Statement: [Outer Gods, existenceRealm, beyond conventional space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceRealm Context triple: [Outer Gods, existenceRealm, beyond conventional space]
-
A.
existenceScope
Indicates the contextual or situational bounds within which an entity or condition is considered to exist or hold true.
-
B.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
C.
residesInRealm
chosen
Indicates that an entity lives or exists within a particular realm or domain.
-
D.
birthRealm
Indicates the realm, world, or plane in which an entity was born.
-
E.
existsBecauseOf
Indicates that one entity’s existence is caused, enabled, or brought about by 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:01 a.m.