Triple
T756129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Natural History of Religion |
E15559
|
entity |
| Predicate | workSeriesContext |
P1761
|
FINISHED |
| Object | Hume’s writings on religion |
—
|
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: Hume’s writings on religion | Statement: [The Natural History of Religion, workSeriesContext, Hume’s writings on religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSeriesContext Context triple: [The Natural History of Religion, workSeriesContext, Hume’s writings on religion]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
isSeriesOf
chosen
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
C.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
D.
followsWork
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6693cbc8190a167e12a896d7ce7 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.