Triple
T36962339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitecliff |
E914339
|
entity |
| Predicate | followsCanon |
P24016
|
FINISHED |
| Object | Dishonored series lore |
—
|
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: Dishonored series lore | Statement: [Whitecliff, followsCanon, Dishonored series lore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCanon Context triple: [Whitecliff, followsCanon, Dishonored series lore]
-
A.
followsInCanon
chosen
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
B.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
eraInCanon
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
-
D.
followsInUniverse
Indicates that one entity chronologically or logically comes after another within a specific fictional or defined universe or continuity.
-
E.
followsInFranchise
Indicates that one work or installment comes after another within the same franchise’s internal sequence or continuity.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.