Triple
T295230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Carnegie |
E6077
|
entity |
| Predicate | hasClanCrest |
P9525
|
FINISHED |
| Object | Crowned thunderbolt between two wings |
—
|
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: Crowned thunderbolt between two wings | Statement: [Clan Carnegie, hasClanCrest, Crowned thunderbolt between two wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanCrest Context triple: [Clan Carnegie, hasClanCrest, Crowned thunderbolt between two wings]
-
A.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
B.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
C.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
E.
primaryEmblem
chosen
Indicates that one emblem is the main or most representative symbol associated with an 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.