Triple
T25088348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mistborn series |
E628384
|
entity |
| Predicate | hasShortFiction |
P143866
|
FINISHED |
| Object | Mistborn: Secret History |
—
|
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: Mistborn: Secret History | Statement: [Mistborn series, hasShortFiction, Mistborn: Secret History]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortFiction Context triple: [Mistborn series, hasShortFiction, Mistborn: Secret History]
-
A.
hasWrittenFiction
Indicates that one entity is the creator or author of fictional written works associated with another entity.
-
B.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
C.
hasNovella
chosen
Indicates that one entity possesses, includes, or is associated with a novella as part of its contents or attributes.
-
D.
hasAssociatedWorkOfFiction
Indicates that an entity is linked to a related work of fiction, such as a novel, film, or story that is associated with it.
-
E.
shortStoryPublicationContext
Indicates the context or medium in which a short story is published, such as the venue, format, or circumstances of its release.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461e667a48190ad63646978cadf62 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:24 a.m.