Triple
T33449926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Saxony-Anhalt |
E856607
|
entity |
| Predicate | tinctureOrRepresents |
P157127
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Coat of arms of Saxony-Anhalt, tinctureOrRepresents, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOrRepresents Context triple: [Coat of arms of Saxony-Anhalt, tinctureOrRepresents, gold]
-
A.
tinctureSystem
Indicates that one entity is part of, or associated with, a tincture system used for preparing or organizing tinctures.
-
B.
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.
-
C.
tinctureRed
Indicates that an entity has a red-colored tincture (heraldic coloring) applied to it.
-
D.
isDepictedInTinctures
chosen
Indicates that an entity is represented using specific heraldic colors or tinctures in a depiction.
-
E.
tinctureOfInscription
Indicates a relationship where an inscription is embodied, preserved, or represented in the form of a tincture or liquid medium.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4aa66108190b8bf569c6fd53030 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.