Triple
T34550002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melverley |
E887035
|
entity |
| Predicate | hasTimberFramedChurch |
P194959
|
FINISHED |
| Object | St Peter's Church, Melverley |
—
|
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: St Peter's Church, Melverley | Statement: [Melverley, hasTimberFramedChurch, St Peter's Church, Melverley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimberFramedChurch Context triple: [Melverley, hasTimberFramedChurch, St Peter's Church, Melverley]
-
A.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
-
B.
hasTimberFramedStreet
Indicates that a location or area contains a street characterized by timber-framed buildings along it.
-
C.
isHistoricChurchIn
Indicates that a church, recognized as historic, is located within a specified geographic area or jurisdiction.
-
D.
hasVillageChurchCharacter
Indicates that something possesses the qualities or characteristics typically associated with a village church.
-
E.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
- F. None of above. chosen
Provenance (4 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 1, 2026, 2:02 a.m.