Triple
T31657475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Wyman |
E807895
|
entity |
| Predicate | laterPersonalityTrait |
P192151
|
FINISHED |
| Object | romantic |
—
|
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: romantic | Statement: [Charlie Wyman, laterPersonalityTrait, romantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPersonalityTrait Context triple: [Charlie Wyman, laterPersonalityTrait, romantic]
-
A.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
B.
secondaryCharacterTrait
Indicates that a secondary or supporting character possesses a particular attribute, quality, or personality trait.
-
C.
hasPersonalityDescribedAs
chosen
Indicates that an entity possesses a personality characterized or labeled in a particular way.
-
D.
usedPersonality
Indicates that one entity employed or applied another entity’s personality, traits, or persona in some context or interaction.
-
E.
personalityType
Indicates the specific psychological or behavioral profile that characterizes an entity’s typical patterns of thinking, feeling, and acting.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 30, 2026, 10:55 p.m.