Triple
T29160429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Shermer |
E739170
|
entity |
| Predicate | wroteSubtitle |
P166374
|
FINISHED |
| Object | The Case Against Intelligent Design |
—
|
NE NERFINISHED |
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: The Case Against Intelligent Design | Statement: [Michael Shermer, wroteSubtitle, The Case Against Intelligent Design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteSubtitle Context triple: [Michael Shermer, wroteSubtitle, The Case Against Intelligent Design]
-
A.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
B.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
C.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
D.
subtitleDFunction
Indicates a functional relationship where one entity serves as the subtitle or secondary textual label for another entity.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d140a48190ac5910abdba5a91c |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:47 a.m.