Triple
T27639961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operating Thetan |
E696562
|
entity |
| Predicate | consideredHigherStateThan |
P13790
|
FINISHED |
| Object | Clear (Scientology) |
E1782504
|
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: Clear (Scientology) | Statement: [Operating Thetan, consideredHigherStateThan, Clear (Scientology)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredHigherStateThan Context triple: [Operating Thetan, consideredHigherStateThan, Clear (Scientology)]
-
A.
isHigherThan
chosen
Indicates that one entity has a greater value, level, or position than another entity.
-
B.
hasHigherInstance
Indicates that one instance in a hierarchy or ordering is ranked or valued higher than another instance.
-
C.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
D.
hasHigherNorm
Indicates that one entity’s norm (such as magnitude, length, or size under a given norm) is greater than that of another entity.
-
E.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
- F. None of above.
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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12e4475b288190979f9e67f1605150 |
completed | May 24, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:25 p.m.