Triple
T531042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Mason |
E12221
|
entity |
| Predicate | symbolismIncludes |
P15163
|
FINISHED |
| Object | death and resurrection allegory |
—
|
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 and resurrection allegory | Statement: [Master Mason, symbolismIncludes, death and resurrection allegory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismIncludes Context triple: [Master Mason, symbolismIncludes, death and resurrection allegory]
-
A.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
C.
symbolDescription
chosen
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
D.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
E.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.