Triple
T10438141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | leeuwendaalder |
E246094
|
entity |
| Predicate | hasIconographyTheme |
P37076
|
FINISHED |
| Object | heraldic lion |
—
|
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: heraldic lion | Statement: [leeuwendaalder, hasIconographyTheme, heraldic lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconographyTheme Context triple: [leeuwendaalder, hasIconographyTheme, heraldic lion]
-
A.
hasIconographicTradition
Indicates that an entity is associated with a recognized, recurring set of visual motifs or symbolic representations within a particular artistic or cultural tradition.
-
B.
hasIconographicFigure
chosen
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
C.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
-
D.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
E.
iconographicCategory
Indicates the classification of an entity based on the type or theme of its visual or symbolic representation.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:14 p.m.