Triple
T32428707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunters of Dune |
E828652
|
entity |
| Predicate | basedOnNotesBy |
P196553
|
FINISHED |
| Object | Frank Herbert |
—
|
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: Frank Herbert | Statement: [Hunters of Dune, basedOnNotesBy, Frank Herbert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnNotesBy Context triple: [Hunters of Dune, basedOnNotesBy, Frank Herbert]
-
A.
basedOnNotesOf
chosen
Indicates that something is created, derived, or developed using another entity’s notes as its primary source or foundation.
-
B.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
C.
baseNote
Indicates that one entity serves as the fundamental or reference note upon which another musical element (such as a chord, scale, or interval) is built or defined.
-
D.
hasBaseNote
Indicates that one entity serves as the fundamental or underlying note upon which another entity (such as a chord, scale, or musical structure) is built.
-
E.
baseNotes
Indicates the fundamental or underlying elements, tones, or components that serve as the primary basis for something.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 1, 2026, 12:54 a.m.