Triple
T35913852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Peter’s Church, Nottingham |
E1038692
|
entity |
| Predicate | hasRegularServices |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularServices Context triple: [St Peter’s Church, Nottingham, hasRegularServices, true]
-
A.
hasRegularServicePattern
chosen
Indicates that an entity consistently follows a defined, recurring schedule or pattern of service over time.
-
B.
hasServiceStandard
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
-
C.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
D.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- F. None of above.
Provenance (1 batch)
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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.