Triple
T33672976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nedre Eiker coat of arms |
E862672
|
entity |
| Predicate | isFormerCoatOfArmsOf |
P1663
|
FINISHED |
| Object | Nedre Eiker municipality |
—
|
NE NERFINISHED |
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: Nedre Eiker municipality | Statement: [Nedre Eiker coat of arms, isFormerCoatOfArmsOf, Nedre Eiker municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerCoatOfArmsOf Context triple: [Nedre Eiker coat of arms, isFormerCoatOfArmsOf, Nedre Eiker municipality]
-
A.
replacedOnCoatOfArmsBy
Indicates that one element or symbol on a coat of arms has been superseded and taken the place of by another element or symbol.
-
B.
coatOfArms
chosen
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
C.
coatOfArmsUsedUntil
Indicates the time or date up to which a particular coat of arms was in official or customary use.
-
D.
designerOfCoatOfArms
Indicates that one entity is the creator or designer responsible for the coat of arms associated with another entity.
-
E.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa3de7a48190809a0a4a7e42c697 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.