Triple
T36899697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Archdiocese of Toledo |
E911995
|
entity |
| Predicate | externalOrnaments |
P23430
|
FINISHED |
| Object | processional cross |
—
|
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: processional cross | Statement: [Coat of arms of the Archdiocese of Toledo, externalOrnaments, processional cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: externalOrnaments Context triple: [Coat of arms of the Archdiocese of Toledo, externalOrnaments, processional cross]
-
A.
ornamentationStyle
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
-
B.
notableOrnamental
Indicates that something is recognized as a particularly significant or distinguished example of ornamental decoration or design.
-
C.
adornedWith
chosen
Indicates that one entity is decorated, embellished, or ornamented by another entity.
-
D.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
E.
orderOrDecoration
Indicates that an entity has been awarded or holds a specific order, honor, or decoration.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd933a488190a99dd4af4f148a20 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.