Triple
T27639871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thetan |
E696560
|
entity |
| Predicate | roleInScientology |
P193704
|
FINISHED |
| Object | central concept of personhood |
—
|
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: central concept of personhood | Statement: [Thetan, roleInScientology, central concept of personhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInScientology Context triple: [Thetan, roleInScientology, central concept of personhood]
-
A.
inTheosophyRole
Indicates that an entity holds or is assigned a particular role or function within the context of Theosophy or a theosophical framework.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
roleInTaoism
Indicates the specific function, status, or position an entity holds within the beliefs, practices, or institutional structure of Taoism.
-
D.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
E.
roleInTranscendence
Indicates that an entity plays a specific role or function in another entity’s process, state, or act of transcendence.
- F. None of above. chosen
Provenance (4 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: April 27, 2026, 2:25 p.m.