Triple
T27639899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thetan |
E696560
|
entity |
| Predicate | ultimateGoalInScientology |
P150465
|
FINISHED |
| Object | full spiritual freedom |
—
|
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: full spiritual freedom | Statement: [Thetan, ultimateGoalInScientology, full spiritual freedom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateGoalInScientology Context triple: [Thetan, ultimateGoalInScientology, full spiritual freedom]
-
A.
goalOfDoctrine
Indicates that a specified objective or end state is the intended goal or purpose of a particular doctrine.
-
B.
centralGoal
chosen
Indicates that something is the primary objective or main aim around which other actions, plans, or considerations are organized.
-
C.
goalOfRealization
Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
-
D.
ultimateRealityTerm
Indicates that the subject term refers to, denotes, or is used to describe the ultimate reality or fundamental nature of existence.
-
E.
finalGoalBelief
Indicates that an agent holds a belief about what the ultimate or end goal of a process, plan, or sequence of actions is.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:25 p.m.