Triple
T35009333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Atom |
E1009902
|
entity |
| Predicate | primaryBelief |
P40063
|
FINISHED |
| Object | worship of radiation as divine |
—
|
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: worship of radiation as divine | Statement: [Children of Atom, primaryBelief, worship of radiation as divine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBelief Context triple: [Children of Atom, primaryBelief, worship of radiation as divine]
-
A.
originBelief
Indicates a belief or assumption about where something or someone comes from or originated.
-
B.
hasCentralBelief
chosen
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
-
C.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
D.
mainFaith
Indicates that one entity is the primary or predominant religious belief or faith tradition associated with another entity.
-
E.
domainOfBelief
Indicates the conceptual area or subject matter that a particular belief pertains to or is about.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.