Triple
T22251389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Morte amoureuse |
E549986
|
entity |
| Predicate | ClarimondeRole |
P147556
|
FINISHED |
| Object | vampiric femme fatale |
—
|
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: vampiric femme fatale | Statement: [La Morte amoureuse, ClarimondeRole, vampiric femme fatale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ClarimondeRole Context triple: [La Morte amoureuse, ClarimondeRole, vampiric femme fatale]
-
A.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
B.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
C.
GameOfThronesRole
Indicates that one entity plays, voices, or otherwise portrays a character in the television series "Game of Thrones" in relation to another entity.
-
D.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
E.
covenRole
Indicates that an entity holds a specific role or position within a coven.
- F. None of above. chosen
Provenance (4 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138befa208190877760dec1896740 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:39 p.m.