Triple
T20708933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian state arms |
E508980
|
entity |
| Predicate | tinctureOfAxeHead |
P24012
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [Norwegian state arms, tinctureOfAxeHead, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tinctureOfAxeHead Context triple: [Norwegian state arms, tinctureOfAxeHead, silver]
-
A.
tinctureOfAxe
Indicates that one entity is a tincture (medicinal or extract preparation) derived from or associated with an axe.
-
B.
axeBladeTincture
chosen
Indicates that the blade of an axe is assigned a specific heraldic tincture (color or pattern).
-
C.
tinctureOfEagle
Indicates a relationship where something is a tincture (an extract or solution) derived from or associated with an eagle.
-
D.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
E.
tinctureOfMace
Indicates that an entity is a medicinal or flavoring preparation made by extracting the active components of mace (the spice) into a solvent, typically alcohol.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1961090819090daf7254f90a176 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.