Triple
T35717339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De vrouw met de sleutel en andere verhalen |
E1032064
|
entity |
| Predicate | hasDuplicateTitleNote |
P183853
|
FINISHED |
| Object | duplicate title |
—
|
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: duplicate title | Statement: [De vrouw met de sleutel en andere verhalen, hasDuplicateTitleNote, duplicate title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDuplicateTitleNote Context triple: [De vrouw met de sleutel en andere verhalen, hasDuplicateTitleNote, duplicate title]
-
A.
hasTitleNote
Indicates that an entity has an associated note or annotation specifically about its title.
-
B.
isUniqueTitle
Indicates that a title is distinct and not shared by any other entity within the relevant context or collection.
-
C.
hasCommonTitle
Indicates that two or more entities share the same title or designation.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.