Triple
T13463807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Rutland |
E311439
|
entity |
| Predicate | hasHeraldryType |
P110465
|
FINISHED |
| Object | coat of arms |
—
|
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: coat of arms | Statement: [Dukes of Rutland, hasHeraldryType, coat of arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeraldryType Context triple: [Dukes of Rutland, hasHeraldryType, coat of arms]
-
A.
hasHeraldicRole
Indicates that an entity holds or is assigned a specific role or function within a heraldic context (such as in coats of arms, armorial bearings, or heraldic ceremonies).
-
B.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
C.
hasHeraldicSubject
Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
-
D.
hasHeraldicBasis
Indicates that something is founded on, derived from, or justified by heraldic principles, symbols, or traditions.
-
E.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
- F. None of above. chosen
Provenance (4 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:41 p.m.