Triple
T21000626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunsfold |
E517275
|
entity |
| Predicate | churchGradeListing |
P142424
|
FINISHED |
| Object | Grade I listed building |
—
|
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: Grade I listed building | Statement: [Dunsfold, churchGradeListing, Grade I listed building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchGradeListing Context triple: [Dunsfold, churchGradeListing, Grade I listed building]
-
A.
churchListingStatus
Indicates the current status or state of a church’s inclusion in a listing or directory (e.g., active, inactive, pending).
-
B.
schoolClassification
Indicates how a school is categorized within an educational system, such as by level, type, or other official classification.
-
C.
schoolSector
Indicates the educational sector or category (such as public, private, or charter) to which a school belongs.
-
D.
hasParochialSchool
Indicates that an entity operates, is associated with, or includes a parochial (religious-affiliated) school.
-
E.
housesDiscipline
Indicates that one entity serves as the location, container, or institutional home for a particular discipline or field of study.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc24a6dc8190a6bf81cf1d9590c0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:52 p.m.