Triple
T16378256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shardlake series |
E397731
|
entity |
| Predicate | protagonistPhysicalTrait |
P21469
|
FINISHED |
| Object | hunchback |
—
|
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: hunchback | Statement: [Shardlake series, protagonistPhysicalTrait, hunchback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistPhysicalTrait Context triple: [Shardlake series, protagonistPhysicalTrait, hunchback]
-
A.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
B.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
C.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
protagonistField
Indicates that the subject is the main or central character (protagonist) within the specified narrative or context.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d97e00819094aa094f52a5a93e |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.