Triple
T26558508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janna Ordonia |
E666176
|
entity |
| Predicate | tropes |
P151325
|
FINISHED |
| Object | Deadpan Snarker |
—
|
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: Deadpan Snarker | Statement: [Janna Ordonia, tropes, Deadpan Snarker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tropes Context triple: [Janna Ordonia, tropes, Deadpan Snarker]
-
A.
usedAsTrope
Indicates that something functions as a recurring narrative device, motif, or cliché within a story or set of stories.
-
B.
inspiredTrope
Indicates that one trope serves as the creative or conceptual inspiration for another trope.
-
C.
subvertsTrope
Indicates that one entity challenges, undermines, or reverses the expected pattern or convention represented by a particular trope.
-
D.
notableTraitInFiction
chosen
Indicates that a particular trait, characteristic, or quality is especially prominent or defining for an entity within fictional works.
-
E.
narrativeMotif
Indicates a recurring thematic element, pattern, or situation that appears across one or more narratives and helps structure or convey their underlying meanings.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614697efc81909cba4b98b198b27e |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:51 a.m.