Triple
T31289650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ślepowron coat of arms |
E797897
|
entity |
| Predicate | tinctureHorseshoe |
P93570
|
FINISHED |
| Object | or |
—
|
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: or | Statement: [Ślepowron coat of arms, tinctureHorseshoe, or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureHorseshoe Context triple: [Ślepowron coat of arms, tinctureHorseshoe, or]
-
A.
tinctureOfKey
Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from, containing, or primarily based on another entity designated as the key ingredient.
-
B.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
C.
horseTincture
chosen
Indicates that an entity (such as a heraldic charge or symbol) bears the tincture or color specifically associated with a horse.
-
D.
tinctureOrdinary
Indicates that an ordinary (a basic heraldic shape or charge) is depicted with a specific tincture (color, metal, or fur) in a coat of arms.
-
E.
tinctureOfField
Indicates that one entity is a tincture (medicinal extract or solution) derived from, based on, or primarily composed of another entity representing a field or source material.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:14 p.m.