Triple
T28176782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bourbon-Maine |
E715912
|
entity |
| Predicate | heraldicHouse |
P913
|
FINISHED |
| Object | Bourbon |
—
|
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: Bourbon | Statement: [House of Bourbon-Maine, heraldicHouse, Bourbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldicHouse Context triple: [House of Bourbon-Maine, heraldicHouse, Bourbon]
-
A.
heraldicName
Indicates the formal name or designation assigned to a heraldic element (such as a coat of arms, charge, or symbol) within a heraldic system.
-
B.
houseSigil
Indicates the emblem or symbol that represents a particular house or family.
-
C.
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.
-
D.
heraldicConnection
Indicates a relationship where entities are linked through heraldry, such as by shared coats of arms, heraldic symbols, lineage, or official armorial associations.
-
E.
heraldicAspect
Indicates a relationship where one entity serves as a heraldic feature, attribute, or component in the coat of arms or heraldic representation of 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:17 p.m.