Triple
T17601134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novilara inscriptions |
E428702
|
entity |
| Predicate | iconographyAssociated |
P49031
|
FINISHED |
| Object | naval battle scene |
—
|
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: naval battle scene | Statement: [Novilara inscriptions, iconographyAssociated, naval battle scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconographyAssociated Context triple: [Novilara inscriptions, iconographyAssociated, naval battle scene]
-
A.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
-
B.
iconographyFeature
Indicates a visual element or motif that appears as a distinct feature within a work’s iconography.
-
C.
iconographicCategory
Indicates the classification of an entity based on the type or theme of its visual or symbolic representation.
-
D.
iconographicSubject
chosen
Indicates that one entity serves as the depicted subject or theme represented in the iconography of another entity.
-
E.
iconographicSource
Indicates that one entity serves as the visual or symbolic source, model, or reference for the iconography or imagery 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c48dfc08190ba360e6082cffa87 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.