Triple
T27639928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clear (Scientology) |
E696561
|
entity |
| Predicate | formalRecognitionMethod |
P8407
|
FINISHED |
| Object | Clear cognition |
—
|
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: Clear cognition | Statement: [Clear (Scientology), formalRecognitionMethod, Clear cognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalRecognitionMethod Context triple: [Clear (Scientology), formalRecognitionMethod, Clear cognition]
-
A.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
B.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
-
C.
confersRecognition
Indicates that one entity formally acknowledges, honors, or grants recognition to another entity for some quality, status, or achievement.
-
D.
isFormalizedBy
chosen
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
E.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:25 p.m.