Triple
T33149754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckinghamshire |
E848401
|
entity |
| Predicate | coatOfArmsBearerFamily |
P913
|
FINISHED |
| Object | Hobart family |
—
|
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: Hobart family | Statement: [Earl of Buckinghamshire, coatOfArmsBearerFamily, Hobart family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsBearerFamily Context triple: [Earl of Buckinghamshire, coatOfArmsBearerFamily, Hobart family]
-
A.
hasHeraldicFamily
chosen
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
-
D.
coatOfArmsSubject
Indicates that a particular coat of arms belongs to, represents, or is associated with a specific subject (such as a person, family, or organization).
-
E.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.