Triple
T30130919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Hendred |
E765841
|
entity |
| Predicate | hasHistoricChapel |
P34531
|
FINISHED |
| Object | Chapel of Jesus of Bethlehem, East Hendred |
—
|
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: Chapel of Jesus of Bethlehem, East Hendred | Statement: [East Hendred, hasHistoricChapel, Chapel of Jesus of Bethlehem, East Hendred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricChapel Context triple: [East Hendred, hasHistoricChapel, Chapel of Jesus of Bethlehem, East Hendred]
-
A.
hasChapels
chosen
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
B.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
C.
eraOfOriginalChapel
Indicates the historical time period during which the original chapel associated with an entity was first constructed or established.
-
D.
hasChapelHonoring
Indicates that one entity contains or includes a chapel dedicated to honoring another entity.
-
E.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 7:15 p.m.