Triple
T37682481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcham |
E938273
|
entity |
| Predicate | hasParishChurchGradeListing |
P142424
|
FINISHED |
| Object | Grade II* 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 II* listed building | Statement: [Marcham, hasParishChurchGradeListing, Grade II* listed building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishChurchGradeListing Context triple: [Marcham, hasParishChurchGradeListing, Grade II* listed building]
-
A.
hasParishChurchListingCategory
Indicates the specific classification or category assigned to a parish church within a defined listing or registry system.
-
B.
hasParishChurchArchitecturalInterest
Indicates that a parish church possesses notable architectural features or significance.
-
C.
heritageListingOfMainChurch
Indicates that a given heritage listing applies specifically to the main church of a place or institution.
-
D.
parishChurchHeritageStatus
Indicates the officially recognized heritage or protection status assigned to a parish church.
-
E.
churchGradeListing
chosen
Indicates a relationship where a church is assigned or associated with a specific grade, rating, or classification in a listing or registry.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:18 p.m.