Triple
T17213496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curse of the Claw |
E417790
|
entity |
| Predicate | hasTitleObject |
P110033
|
FINISHED |
| Object | cursed claw relic |
—
|
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: cursed claw relic | Statement: [The Curse of the Claw, hasTitleObject, cursed claw relic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleObject Context triple: [The Curse of the Claw, hasTitleObject, cursed claw relic]
-
A.
hasTitleObjectInPlot
chosen
Indicates that an entity’s title explicitly appears as an object or element within the narrative plot of a work.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
D.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
-
E.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc795d08190b90801a4f8b23afe |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.