Triple
T28235067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauda coat of arms |
E711855
|
entity |
| Predicate | tinctureOfHammer |
P164142
|
FINISHED |
| Object | argent |
—
|
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: argent | Statement: [Sauda coat of arms, tinctureOfHammer, argent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOfHammer Context triple: [Sauda coat of arms, tinctureOfHammer, argent]
-
A.
tinctureOfEagle
Indicates a relationship where something is a tincture (an extract or solution) derived from or associated with an eagle.
-
B.
tinctureOfLion
Indicates a relationship where something is a medicinal or alchemical preparation (a “tincture”) derived from or associated with a lion.
-
C.
tinctureOfAxe
Indicates that one entity is a tincture (medicinal or extract preparation) derived from or associated with an axe.
-
D.
tinctureOfSword
Indicates that something is a medicinal or alchemical tincture prepared from, associated with, or derived from a sword.
-
E.
tinctureOfPale
Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from or characterized by the pale aspect, quality, or component of another entity.
- F. None of above. chosen
Provenance (4 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6438cc14481908bb8f1728596c16b |
completed | May 2, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:54 p.m.