Triple
T31734564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black Book |
E809956
|
entity |
| Predicate | hasItemInPlot |
P53895
|
FINISHED |
| Object | mysterious notebook |
—
|
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: mysterious notebook | Statement: [The Black Book, hasItemInPlot, mysterious notebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasItemInPlot Context triple: [The Black Book, hasItemInPlot, mysterious notebook]
-
A.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
B.
isKeyToPlotOf
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
-
C.
hasMainPlotElement
chosen
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
D.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
-
E.
hasAgencyInPlot
Indicates that an entity actively influences or drives events within the narrative’s plot.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab22f464819098766f11b1c3c846 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:22 p.m.