Triple
T25005492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czernobog |
E625829
|
entity |
| Predicate | residenceInAmericanGods |
P120353
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Czernobog, residenceInAmericanGods, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceInAmericanGods Context triple: [Czernobog, residenceInAmericanGods, United States]
-
A.
relatedDeityResidence
Indicates that a deity is associated with, dwells in, or is traditionally believed to reside in a particular place or realm.
-
B.
residentInFiction
chosen
Indicates that one entity is a fictional character or element that resides or exists within the fictional setting, world, or universe represented by another entity.
-
C.
addressesDeity
Indicates that one entity directs speech, prayer, or invocation toward a deity.
-
D.
residencyOf
Indicates that one entity serves as the place where another entity resides or lives.
-
E.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:05 a.m.