Triple
T32937498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chloe |
E842570
|
entity |
| Predicate | hasObsessionPlot |
P49999
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chloe, hasObsessionPlot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObsessionPlot Context triple: [Chloe, hasObsessionPlot, true]
-
A.
obsessionWith
chosen
Indicates an intense, persistent, and often overwhelming preoccupation or fixation that one entity has toward another entity or object.
-
B.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
-
C.
hasPoliticalPlot
Indicates that the subject work contains a storyline or narrative element centered on politics, political events, or political power struggles.
-
D.
hasBlackmailPlot
Indicates that one entity possesses or is involved in a scheme to coerce another entity using compromising or threatening information.
-
E.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d10cb6c481908b0adeef147884ea |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.