Triple
T901789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Thorne |
E19461
|
entity |
| Predicate | centralPlotDevice |
P21187
|
FINISHED |
| Object | hidden inheritance |
—
|
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: hidden inheritance | Statement: [Doctor Thorne, centralPlotDevice, hidden inheritance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlotDevice Context triple: [Doctor Thorne, centralPlotDevice, hidden inheritance]
-
A.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
D.
methodOfDisappearance
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
E.
centralEventOfPiety
Indicates that an event serves as the primary or focal act of religious devotion or pious practice within a given context.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4412408190a6bf8fc7484a5781 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4abb157d08190a7d7281eb3f1b788 |
completed | March 1, 2026, 9:12 p.m. |
Created at: March 1, 2026, 7:39 p.m.