Triple

T26648192
Position Surface form Disambiguated ID Type / Status
Subject Horten municipality E668975 entity
Predicate hasCoatOfArms P1663 FINISHED
Object Horten coat of arms
The Horten coat of arms is the official heraldic emblem of the Norwegian coastal municipality of Horten, symbolizing its maritime heritage and naval history.
E1733623 NE 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: Horten coat of arms | Statement: [Horten municipality, hasCoatOfArms, Horten coat of arms]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Horten coat of arms
Triple: [Horten municipality, hasCoatOfArms, Horten coat of arms]
Generated description
The Horten coat of arms is the official heraldic emblem of the Norwegian coastal municipality of Horten, symbolizing its maritime heritage and naval history.

Provenance (5 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_69ee9d00eb5481908d6c6d0ada2f0c9a completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f616778678819095bc601b19dbe0bd completed May 2, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11ec42d2148190be1debe7b05bfb3f completed May 23, 2026, 6:04 p.m.
NEDg Description generation batch_6a11ecf53a20819083a0f23be7d859a4 completed May 23, 2026, 6:07 p.m.
NED2 Entity disambiguation (via description) batch_6a11edae81bc8190aa626f0cd67562d9 completed May 23, 2026, 6:10 p.m.
Created at: April 27, 2026, 2:32 a.m.