Triple

T36187339
Position Surface form Disambiguated ID Type / Status
Subject Lenham E1046882 entity
Predicate hasLandmark P105 FINISHED
Object Church of St Mary
The Church of St Mary is a historic parish church in the village of Lenham, Kent, notable for its medieval architecture and longstanding role in the local community.
E1577001 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: Church of St Mary | Statement: [Lenham, hasLandmark, Church of St Mary]
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: Church of St Mary
Triple: [Lenham, hasLandmark, Church of St Mary]
Generated description
The Church of St Mary is a historic parish church in the village of Lenham, Kent, notable for its medieval architecture and longstanding role in the local community.

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_69f76e3d4fbc81908c159c7beeb4ce00 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5159e5c81908f8ac93fa29b22ea completed May 3, 2026, 8:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39a30be0588190a9a4b4c7eefe17b4 completed June 22, 2026, 9:03 p.m.
NEDg Description generation batch_6a39a48840c481908820e235af0f820c completed June 22, 2026, 9:09 p.m.
NED2 Entity disambiguation (via description) batch_6a39a6112b988190b72e546fe3958420 completed June 22, 2026, 9:16 p.m.
Created at: May 3, 2026, 4:08 p.m.