Triple
T35119869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six of Crows |
E1014137
|
entity |
| Predicate | prequelOrPreviousWork |
P90756
|
FINISHED |
| Object | Shadow and Bone |
E1014136
|
NE 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: Shadow and Bone | Statement: [Six of Crows, prequelOrPreviousWork, Shadow and Bone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prequelOrPreviousWork Context triple: [Six of Crows, prequelOrPreviousWork, Shadow and Bone]
-
A.
prequelOrSequelTo
Indicates that one work in a narrative series occurs earlier or later in the storyline or release order relative to another work, as its prequel or sequel.
-
B.
isPrequelTo
Indicates that one work or event occurs earlier in time and narratively sets up or leads into another work or event.
-
C.
prequelAppearance
Indicates that an entity appears in a work that is a prequel to another related work or installment.
-
D.
previousWorkInSeries
chosen
Indicates that one work directly precedes another within the same series or sequence.
-
E.
precededByFilmAdaptationOfSameNovel
Indicates that the subject film was released after, and is chronologically preceded by, another film adaptation of the same source novel.
- F. None of above.
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d94edb588190871370aa0a3fd359 |
completed | June 21, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.