Triple
T29754276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talbot hound |
E752986
|
entity |
| Predicate | commonHeraldicPose |
P37998
|
FINISHED |
| Object | sejant |
—
|
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: sejant | Statement: [Talbot hound, commonHeraldicPose, sejant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonHeraldicPose Context triple: [Talbot hound, commonHeraldicPose, sejant]
-
A.
coatOfArmsPosition
Indicates the spatial placement or arrangement of a coat of arms relative to another object, surface, or reference frame.
-
B.
hasHeraldicAttitude
chosen
Indicates that an entity (typically an animal or figure in heraldry) is depicted with a specific standardized posture or stance in a coat of arms.
-
C.
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.
-
D.
hasHeraldicOrientation
Indicates the directional or positional orientation of a heraldic element within a coat of arms or similar heraldic context.
-
E.
heraldicCharge
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.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 28, 2026, 7:55 p.m.