Triple
T31289668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ślepowron coat of arms |
E797897
|
entity |
| Predicate | relatedCoatOfArms |
P77925
|
FINISHED |
| Object | Krasiński coat of arms variant |
—
|
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: Krasiński coat of arms variant | Statement: [Ślepowron coat of arms, relatedCoatOfArms, Krasiński coat of arms variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCoatOfArms Context triple: [Ślepowron coat of arms, relatedCoatOfArms, Krasiński coat of arms variant]
-
A.
hasCoatOfArmsSharedWith
Indicates that two entities share the same coat of arms design or heraldic emblem.
-
B.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
designerOfCoatOfArms
Indicates that one entity is the creator or designer responsible for the coat of arms associated with another entity.
-
D.
hasCoatOfArmsFeature
Indicates that an entity’s coat of arms includes or displays a specific feature or element.
-
E.
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.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:14 p.m.