Triple
T7619325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross |
E172446
|
entity |
| Predicate | inspiredArtForm |
P62284
|
FINISHED |
| Object | Christian iconography |
—
|
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: Christian iconography | Statement: [Holy Cross, inspiredArtForm, Christian iconography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredArtForm Context triple: [Holy Cross, inspiredArtForm, Christian iconography]
-
A.
inspiredArtMovement
Indicates that one entity served as a creative or conceptual influence leading to the development or direction of an art movement in the other entity.
-
B.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
-
C.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
-
D.
inspiredWorksOf
chosen
Indicates that one entity served as the source of inspiration or creative influence for the works produced by another entity.
-
E.
artisticField
Indicates the artistic domain or creative discipline in which an entity is active or associated.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.