Triple
T29237300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clockwork Angels |
E741226
|
entity |
| Predicate | companionNovelStoryBy |
P2758
|
FINISHED |
| Object | Neil Peart |
—
|
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: Neil Peart | Statement: [Clockwork Angels, companionNovelStoryBy, Neil Peart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionNovelStoryBy Context triple: [Clockwork Angels, companionNovelStoryBy, Neil Peart]
-
A.
hasCompanionBook
chosen
Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
-
B.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
C.
narratorCompanion
Indicates that one entity serves as a companion or close associate to the narrator within the context of a narrative or account.
-
D.
associatedTale
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
E.
associatedWithAuthorOfSourceNovel
Indicates a relationship where one entity is connected or linked in some way to the author of the original source novel.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 12:30 p.m.