Triple
T37910185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feel My Pulse |
E945663
|
entity |
| Predicate | basedInPartOnCharacterType |
P180826
|
FINISHED |
| Object | hypochondriac heiress |
—
|
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: hypochondriac heiress | Statement: [Feel My Pulse, basedInPartOnCharacterType, hypochondriac heiress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInPartOnCharacterType Context triple: [Feel My Pulse, basedInPartOnCharacterType, hypochondriac heiress]
-
A.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
B.
usedForCharacterType
Indicates that something is intended to be used for, or is suitable for, a particular type of character.
-
C.
controlledCharacterType
Indicates that one entity specifies or constrains the type or category of character that another entity is allowed to control.
-
D.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
E.
employsCharacterType
chosen
Indicates that an entity makes use of or features a particular type or category of character in its content or structure.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:20 p.m.