Triple
T7906984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scientology |
E183600
|
entity |
| Predicate | isCriticalOf |
P69159
|
FINISHED |
| Object | psychiatry |
—
|
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: psychiatry | Statement: [Scientology, isCriticalOf, psychiatry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCriticalOf Context triple: [Scientology, isCriticalOf, psychiatry]
-
A.
hasCriticalConcept
Indicates that one entity includes, depends on, or is defined by a key concept that is essential to understanding or functioning of another entity.
-
B.
hasCriticalView
chosen
Indicates that one entity holds a negative, skeptical, or evaluative stance toward another entity, often highlighting flaws, problems, or points of disagreement.
-
C.
timeCriticalFor
Indicates that one entity must occur, be addressed, or be completed within a strict or urgent time frame in relation to another entity or condition.
-
D.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
E.
firstCriticalityUnit2
Indicates that the referenced entity is the second unit or component associated with the first level or category of criticality.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5871b8819087ad69c116c40091 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.