Triple
T26981567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | För levande och döda |
E679613
|
entity |
| Predicate | hasVividImagery |
P64074
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [För levande och döda, hasVividImagery, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVividImagery Context triple: [För levande och döda, hasVividImagery, true]
-
A.
isAssociatedWithChildhoodImagery
Indicates a relationship where something is linked to, evokes, or prominently features imagery commonly connected with childhood.
-
B.
hasColorImagery
Indicates that something includes or is characterized by visual elements emphasizing specific colors or color-based symbolism.
-
C.
usesImageryOf
Indicates that one entity employs or incorporates visual or sensory imagery that depicts, references, or symbolically represents another entity.
-
D.
usesImagery
chosen
Indicates that one entity employs descriptive or figurative language to create sensory or vivid mental images in relation to another entity or concept.
-
E.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 6:46 a.m.