Triple
T11170532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Astorga |
E264260
|
entity |
| Predicate | hasCoatOfArmsType |
P58180
|
FINISHED |
| Object | ecclesiastical heraldry |
—
|
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: ecclesiastical heraldry | Statement: [Roman Catholic Diocese of Astorga, hasCoatOfArmsType, ecclesiastical heraldry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoatOfArmsType Context triple: [Roman Catholic Diocese of Astorga, hasCoatOfArmsType, ecclesiastical heraldry]
-
A.
coatOfArmsType
chosen
Indicates the specific kind or category of coat of arms associated with an entity.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
usesCoatOfArmsVariant
Indicates that an entity employs an alternative or modified version of a standard coat of arms rather than the primary or original design.
-
D.
hasNoCoatOfArmsOnStandardVersion
Indicates that the entity’s standard or default version does not display or include a coat of arms.
-
E.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.