Triple
T27639924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clear (Scientology) |
E696561
|
entity |
| Predicate | achievedThrough |
P162788
|
FINISHED |
| Object | auditing |
—
|
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: auditing | Statement: [Clear (Scientology), achievedThrough, auditing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedThrough Context triple: [Clear (Scientology), achievedThrough, auditing]
-
A.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
B.
coAchieved
Indicates that two or more entities jointly accomplished or attained the same goal, outcome, or achievement.
-
C.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
D.
aspiredTo
Indicates that one entity had a strong desire or ambition to achieve, become, or obtain the other entity.
-
E.
canAchieve
Indicates that an entity has the ability or potential to successfully attain or accomplish a specified goal, state, or outcome.
- 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_69f63190c17c8190a0ee11e09caefc2b |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:25 p.m.