Triple
T33340044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilton, Somerset |
E853643
|
entity |
| Predicate | titheBarnStatus |
P923
|
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: [Pilton, Somerset, titheBarnStatus, Grade I listed building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titheBarnStatus Context triple: [Pilton, Somerset, titheBarnStatus, Grade I listed building]
-
A.
abbeyStatus
Indicates the current religious, administrative, or functional status assigned to an abbey.
-
B.
basilicaStatus
Indicates that an entity holds the official ecclesiastical designation or rank of a basilica within a religious tradition.
-
C.
BugsworthBasinStatus
Indicates the current condition, operational state, or designation of Bugsworth Basin within a given context.
-
D.
heritageStatus
chosen
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
E.
tartanStatus
Indicates the relationship between an entity and its classification or condition regarding tartan (e.g., whether a tartan pattern is official, registered, or has a particular status).
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.