Triple
T31289651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ślepowron coat of arms |
E797897
|
entity |
| Predicate | tinctureCross |
P67841
|
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, tinctureCross, or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureCross Context triple: [Ślepowron coat of arms, tinctureCross, or]
-
A.
tinctureOfCross
chosen
Indicates that something is a tincture (heraldic color or pattern) specifically applied to a cross in a coat of arms or similar symbolic design.
-
B.
tinctureOfCrosses
Indicates a heraldic design in which a field or charge is patterned or strewn with multiple small crosses as a repeated motif.
-
C.
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.
-
D.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
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_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:14 p.m.