Triple
T15542089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Kingairloch |
E370503
|
entity |
| Predicate | coatOfArmsRelationship |
P77925
|
FINISHED |
| Object | bears differenced arms of Clan Maclean |
—
|
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: bears differenced arms of Clan Maclean | Statement: [Maclean of Kingairloch, coatOfArmsRelationship, bears differenced arms of Clan Maclean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsRelationship Context triple: [Maclean of Kingairloch, coatOfArmsRelationship, bears differenced arms of Clan Maclean]
-
A.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
B.
hasCoatOfArmsSharedWith
Indicates that two entities share the same coat of arms design or heraldic emblem.
-
C.
heraldicConnection
chosen
Indicates a relationship where entities are linked through heraldry, such as by shared coats of arms, heraldic symbols, lineage, or official armorial associations.
-
D.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an entity.
-
E.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04432c3808190bb5b653bf8de30c6 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.