Triple
T37887360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelling, Cambridgeshire |
E945034
|
entity |
| Predicate | servedByClergyman |
P9815
|
FINISHED |
| Object | Henry Venn |
—
|
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: Henry Venn | Statement: [Yelling, Cambridgeshire, servedByClergyman, Henry Venn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByClergyman Context triple: [Yelling, Cambridgeshire, servedByClergyman, Henry Venn]
-
A.
clergyMayBe
Indicates that an individual is permitted or eligible to serve in a clergy role.
-
B.
workedAsClergymanIn
Indicates that a person served in a religious or clerical role within a specified place or institution.
-
C.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
E.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00818b20a881909fbf3bb33dcf7029 |
completed | May 10, 2026, 1 p.m. |
| PD | Predicate disambiguation | batch_6a0080f76f588190a933238861243d1a |
completed | May 10, 2026, 12:58 p.m. |
Created at: May 3, 2026, 4:19 p.m.