Triple
T33052228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forward |
E845756
|
entity |
| Predicate | usedInHeraldryOf |
P61212
|
FINISHED |
| Object | Dukes of Buccleuch and Queensberry |
—
|
NE NERFINISHED |
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: Dukes of Buccleuch and Queensberry | Statement: [Forward, usedInHeraldryOf, Dukes of Buccleuch and Queensberry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInHeraldryOf Context triple: [Forward, usedInHeraldryOf, Dukes of Buccleuch and Queensberry]
-
A.
hasHeraldicUse
chosen
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
-
B.
partOfHeraldryOf
Indicates that something is an element or component included within a specific coat of arms or heraldic system.
-
C.
hasHeraldicMeaning
Indicates that something (typically a symbol, color, or design) carries a specific meaning or significance within the system of heraldry.
-
D.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
E.
usesHeraldicStyle
Indicates that one entity employs or follows the heraldic style, conventions, or visual language associated with 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:24 a.m.