Triple
T32904973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brichester Mythos |
E841709
|
entity |
| Predicate | notableDeityOrEntityOrigin |
P205196
|
FINISHED |
| Object | Severn Valley |
E1165218
|
NE 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: Severn Valley | Statement: [Brichester Mythos, notableDeityOrEntityOrigin, Severn Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeityOrEntityOrigin Context triple: [Brichester Mythos, notableDeityOrEntityOrigin, Severn Valley]
-
A.
deityOrigin
Indicates that one entity is the source, creator, or originating cause of a deity or divine being.
-
B.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
C.
veneratedBeings
Indicates that certain beings are regarded with deep respect, reverence, or worship by others.
-
D.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
E.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- F. None of above. chosen
Provenance (5 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d25b36848190b43cf52355a8913c |
completed | June 19, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:19 a.m.