Triple
T18901438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Word & Void series |
E462348
|
entity |
| Predicate | relationToShannara |
P133724
|
FINISHED |
| Object | thematic prequel |
—
|
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: thematic prequel | Statement: [Word & Void series, relationToShannara, thematic prequel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToShannara Context triple: [Word & Void series, relationToShannara, thematic prequel]
-
A.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
C.
relationshipToSamanthaGrimm
Indicates the specific type of relationship or connection an entity has to Samantha Grimm.
-
D.
relationToTimeLords
Indicates the nature of a subject’s connection, association, or relevance to Time Lords, such as affiliation, interaction, or status in relation to them.
-
E.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52954bc8190a237627c09615ac1 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4afa745c081908da20a51ebc147b4 |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 11:58 a.m.