Triple

T34454882
Position Surface form Disambiguated ID Type / Status
Subject Lebuinus Church E884475 entity
Predicate namedAfter P63 FINISHED
Object Saint Lebuinus
Saint Lebuinus was an Anglo-Saxon missionary priest of the 8th century known for evangelizing in the region of present-day Netherlands, particularly around Deventer.
E2096363 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: Saint Lebuinus | Statement: [Lebuinus Church, namedAfter, Saint Lebuinus]
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: Saint Lebuinus
Triple: [Lebuinus Church, namedAfter, Saint Lebuinus]
Generated description
Saint Lebuinus was an Anglo-Saxon missionary priest of the 8th century known for evangelizing in the region of present-day Netherlands, particularly around Deventer.

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_69f349c607688190b553539d14901a35 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7197619148190b613539880121e74 completed May 3, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37184846ec819090822d7e56bbdd18 completed June 20, 2026, 10:46 p.m.
NEDg Description generation batch_6a3718c84ee481908c220b2564249159 completed June 20, 2026, 10:48 p.m.
NED2 Entity disambiguation (via description) batch_6a37195b2b9c8190a70d9deec095f539 completed June 20, 2026, 10:51 p.m.
Created at: May 1, 2026, 2 a.m.