Triple
T5394776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Arendal |
E120624
|
entity |
| Predicate | anchorTincture |
P24010
|
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: [Coat of arms of Arendal, anchorTincture, or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anchorTincture Context triple: [Coat of arms of Arendal, anchorTincture, or]
-
A.
tressureTincture
Indicates the color or pattern (tincture) applied specifically to a tressure in heraldic design.
-
B.
fieldTincture
Indicates the heraldic tincture (color, metal, or fur) applied to the main background field of a coat of arms.
-
C.
tongueTincture
Indicates that an entity applies or administers a tincture by placing it on or under the tongue.
-
D.
chargeTincture
chosen
Indicates that a heraldic charge bears a specific tincture (color, metal, or fur) in a coat of arms.
-
E.
chiefTincture
Indicates that one entity serves as the primary or dominant coloring or tonal quality in relation to another entity.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87441a208190b79561614759894b |
completed | March 20, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.