Triple
T26874472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Challis |
E676708
|
entity |
| Predicate | hasMultiplePersonalities |
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: [Kay Challis, hasMultiplePersonalities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplePersonalities Context triple: [Kay Challis, hasMultiplePersonalities, yes]
-
A.
hasDifferentPersonalityIn
Indicates that an entity exhibits a different personality or character traits within a specified context, setting, or situation.
-
B.
hasMainPersonality
Indicates that one entity possesses or is characterized by a primary or dominant personality associated with another entity.
-
C.
featuresNumberOfPersonalities
Indicates that an entity is characterized by or contains a specified number of distinct personalities.
-
D.
hasMultipleIdentities
chosen
Indicates that a single entity is associated with more than one distinct identity or persona.
-
E.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 5:34 a.m.