Triple
T17890809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMERSH (in the novel) |
E447309
|
entity |
| Predicate | acronymMeaningInFiction |
P42398
|
FINISHED |
| Object | death to spies |
—
|
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: death to spies | Statement: [SMERSH (in the novel), acronymMeaningInFiction, death to spies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acronymMeaningInFiction Context triple: [SMERSH (in the novel), acronymMeaningInFiction, death to spies]
-
A.
languageWithinFiction
Indicates that a language is used or exists within the context of a fictional work or fictional universe.
-
B.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
-
C.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
D.
acronymExpansion
chosen
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
E.
figurativeMeaning
Indicates that one entity is used in a non-literal, metaphorical, or symbolic sense to convey a meaning about another entity or concept.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7948888190b59ddc7061d13e84 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.