Triple
T27557602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wivelsfield |
E695681
|
entity |
| Predicate | hasBuildingMaterialAtParishChurch |
P134857
|
FINISHED |
| Object | stone construction |
—
|
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: stone construction | Statement: [Wivelsfield, hasBuildingMaterialAtParishChurch, stone construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingMaterialAtParishChurch Context triple: [Wivelsfield, hasBuildingMaterialAtParishChurch, stone construction]
-
A.
parishChurchConstructionMaterial
chosen
Indicates the material from which a parish church is constructed.
-
B.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
C.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
D.
isParishChurchIn
Indicates that a church serves as the designated parish church for a specific parish or locality.
-
E.
hasParishChurchDedication
Indicates that a parish church is dedicated to, or placed under the patronage of, a particular figure, saint, or sacred concept.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 1:37 p.m.