Triple
T38240379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Umber |
E1013744
|
entity |
| Predicate | heraldryElement |
P32838
|
FINISHED |
| Object | Giant |
—
|
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: Giant | Statement: [House Umber, heraldryElement, Giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heraldryElement Context triple: [House Umber, heraldryElement, Giant]
-
A.
heraldicCharge
chosen
Indicates that one entity serves as a heraldic charge, i.e., a symbolic figure or emblem placed on another entity’s coat of arms or shield.
-
B.
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.
-
C.
partOfHeraldryOf
Indicates that something is an element or component included within a specific coat of arms or heraldic system.
-
D.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
E.
heraldicStatus
Indicates the formal standing or classification of an entity within a heraldic system, such as its rank, legitimacy, or official recognition in heraldry.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.