Triple
T20305327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Allegory of Christian Virtue and Vice |
E505594
|
entity |
| Predicate | usesSymbolismFor |
P129
|
FINISHED |
| Object | virtue |
—
|
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: virtue | Statement: [The Allegory of Christian Virtue and Vice, usesSymbolismFor, virtue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSymbolismFor Context triple: [The Allegory of Christian Virtue and Vice, usesSymbolismFor, virtue]
-
A.
incorporatesSymbolismFrom
Indicates that one entity includes or integrates symbolic elements, motifs, or meanings derived from another entity.
-
B.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
C.
symbolismFocus
Indicates that the primary emphasis of a work, element, or representation is on its symbolic meaning rather than its literal or functional aspects.
-
D.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
E.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773f8f688190b616f972b9bbb28e |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:18 a.m.