Triple
T33853776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obsession |
E867709
|
entity |
| Predicate | isExperiencedAs |
P22183
|
FINISHED |
| Object | internal mental events |
—
|
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: internal mental events | Statement: [Obsession, isExperiencedAs, internal mental events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExperiencedAs Context triple: [Obsession, isExperiencedAs, internal mental events]
-
A.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
B.
allegedlyExperienced
Indicates that an entity is claimed or reported to have undergone or had a particular experience, without asserting that the experience actually occurred.
-
C.
hasPastExperience
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
D.
typeOfExperience
chosen
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
usedExperienceIn
Indicates that an entity applied or leveraged a particular experience or expertise in performing an action or achieving a result.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70076bdec8190a109af85bed04c90 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.