Triple
T34392444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank Evans |
E882740
|
entity |
| Predicate | hasSplitPersonalityWith |
P108643
|
FINISHED |
| Object | Charlie Baileygates |
—
|
NE NERFINISHED |
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: Charlie Baileygates | Statement: [Hank Evans, hasSplitPersonalityWith, Charlie Baileygates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSplitPersonalityWith Context triple: [Hank Evans, hasSplitPersonalityWith, Charlie Baileygates]
-
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.
hasMultipleIdentities
chosen
Indicates that a single entity is associated with more than one distinct identity or persona.
-
D.
hasDoppelganger
Indicates that an entity has a counterpart or double that closely resembles it, often in appearance, behavior, or role.
-
E.
hasSiblingPersona
Indicates that one entity has another entity as a sibling persona, representing an alternate or parallel version of the same underlying identity.
- 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_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:59 a.m.