Triple
T12529588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacInnes |
E299525
|
entity |
| Predicate | hasCrestBadge |
P105736
|
FINISHED |
| Object | a hand holding a cross crosslet fitchée Gules |
—
|
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: a hand holding a cross crosslet fitchée Gules | Statement: [Clan MacInnes, hasCrestBadge, a hand holding a cross crosslet fitchée Gules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrestBadge Context triple: [Clan MacInnes, hasCrestBadge, a hand holding a cross crosslet fitchée Gules]
-
A.
hasCrestType
Indicates that an entity possesses a specific type or form of crest.
-
B.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
C.
hasCoronet
Indicates that an entity possesses or is adorned with a coronet (a small crown).
-
D.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
E.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
- F. None of above. chosen
Provenance (4 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.