Triple
T31234579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkness Visible: A Memoir of Madness |
E796378
|
entity |
| Predicate | timeToReadApproximate |
P144899
|
FINISHED |
| Object | a few hours |
—
|
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: a few hours | Statement: [Darkness Visible: A Memoir of Madness, timeToReadApproximate, a few hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToReadApproximate Context triple: [Darkness Visible: A Memoir of Madness, timeToReadApproximate, a few hours]
-
A.
timeRequiredToRead
Indicates the amount of time needed for an entity (such as a person) to read a given item or content.
-
B.
readingTime
chosen
Indicates the duration or amount of time an entity spends (or is expected to spend) reading another entity.
-
C.
typicalViewingTime
Indicates the usual or most common amount of time an entity is viewed or watched under normal circumstances.
-
D.
minimumViewingTime
Indicates the least amount of time an item must be viewed or played for a condition (such as completion, eligibility, or credit) to be considered satisfied.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.