Triple
T18587639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFT |
E454278
|
entity |
| Predicate | mayAlsoStandFor |
P590
|
FINISHED |
| Object | Cognitive fusion therapy |
—
|
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: Cognitive fusion therapy | Statement: [CFT, mayAlsoStandFor, Cognitive fusion therapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoStandFor Context triple: [CFT, mayAlsoStandFor, Cognitive fusion therapy]
-
A.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
B.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
C.
standsFor
chosen
Indicates that one entity represents, symbolizes, or serves as a substitute or abbreviation for another entity.
-
D.
canAlsoIndicate
Indicates that something may additionally signify, represent, or serve as another meaning or function beyond its primary one.
-
E.
mayAlsoAdmit
Indicates that an entity has the option or authority to additionally allow or accept another entity, beyond any primary or default admission.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b2f20481908da74447cd08d5bd |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.