Triple

T27070915
Position Surface form Disambiguated ID Type / Status
Subject Harley family E685321 entity
Predicate hasHeraldicTradition P9680 FINISHED
Object Harley coat of arms
The Harley coat of arms is the heraldic emblem representing the historic English Harley family, traditionally displayed on their seals, monuments, and armorial bearings.
E1752935 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: Harley coat of arms | Statement: [Harley family, hasHeraldicTradition, Harley 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: Harley coat of arms
Triple: [Harley family, hasHeraldicTradition, Harley coat of arms]
Generated description
The Harley coat of arms is the heraldic emblem representing the historic English Harley family, traditionally displayed on their seals, monuments, and armorial bearings.

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_69ef14843b1481909d828b3d5a44550a completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f6231144a481909c26be4250d38932 completed May 2, 2026, 4:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a123ada0dc48190a8f0b839c1860c01 completed May 23, 2026, 11:40 p.m.
NEDg Description generation batch_6a123ba9aea081909f20ff78ab91747e completed May 23, 2026, 11:43 p.m.
NED2 Entity disambiguation (via description) batch_6a123c56268c81909d0e71dad0aeab01 completed May 23, 2026, 11:46 p.m.
Created at: April 27, 2026, 8:28 a.m.