Triple
T30126418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of St Peter and St Paul, Heytesbury |
E765706
|
entity |
| Predicate | villageRole |
P115569
|
FINISHED |
| Object | religious centre of Heytesbury |
—
|
LITERAL 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: religious centre of Heytesbury | Statement: [Church of St Peter and St Paul, Heytesbury, villageRole, religious centre of Heytesbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villageRole Context triple: [Church of St Peter and St Paul, Heytesbury, villageRole, religious centre of Heytesbury]
-
A.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
B.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
C.
servesVillage
chosen
Indicates that an entity provides services, support, or functions that benefit or are directed toward a particular village.
-
D.
ethnographicRole
Indicates the role or function an entity holds within an ethnographic context, such as a cultural, social, or research-related position.
-
E.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67deffb10819082e0bd841b65883e |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:14 p.m.