Triple
T17219367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cloven Viscount |
E417932
|
entity |
| Predicate | workChronologyWithinTrilogy |
P32562
|
FINISHED |
| Object | first volume |
—
|
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: first volume | Statement: [The Cloven Viscount, workChronologyWithinTrilogy, first volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workChronologyWithinTrilogy Context triple: [The Cloven Viscount, workChronologyWithinTrilogy, first volume]
-
A.
chronologicalOrderInOriginalTrilogy
chosen
Indicates the sequence in which events or items appear in time within the original trilogy.
-
B.
workChronologyWithinParallelLives
Indicates that one work’s chronological placement is defined relative to another work within a set of parallel or alternative life narratives.
-
C.
partOfTrilogy
Indicates that one work belongs to a set of three related works that together form a trilogy.
-
D.
hasPartInTrilogy
Indicates that an entity is one of the constituent parts (e.g., books, films, or episodes) that together form a specific trilogy.
-
E.
chronologicalOrderInSeries
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddc3cb88190a67e35164d710d9d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.