Triple
T34392401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Baileygates |
E882739
|
entity |
| Predicate | hasDissociativeIdentity |
P108643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charlie Baileygates, hasDissociativeIdentity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDissociativeIdentity Context triple: [Charlie Baileygates, hasDissociativeIdentity, yes]
-
A.
hasMultipleIdentities
chosen
Indicates that a single entity is associated with more than one distinct identity or persona.
-
B.
hasDifferentPersonalityIn
Indicates that an entity exhibits a different personality or character traits within a specified context, setting, or situation.
-
C.
hasIdentityIssues
Indicates that an entity experiences confusion, uncertainty, or conflict regarding its own identity or sense of self.
-
D.
hasDelusionsAbout
Indicates that one entity experiences delusional beliefs specifically concerning or focused on another entity.
-
E.
hasImaginedIdentity
Indicates that an entity mentally constructs or adopts a non-actual identity, role, or persona for itself or another entity.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:59 a.m.