Triple
T37121252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary’s Church, Wigton |
E919258
|
entity |
| Predicate | roleInLocalArea |
P15115
|
FINISHED |
| Object | local center of worship |
—
|
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: local center of worship | Statement: [St Mary’s Church, Wigton, roleInLocalArea, local center of worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLocalArea Context triple: [St Mary’s Church, Wigton, roleInLocalArea, local center of worship]
-
A.
nearbyRole
Indicates that one role is spatially close to or within a short distance of another role.
-
B.
roleInCommunity
chosen
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
C.
nearbySettlementRole
Indicates that one settlement has a specific functional or contextual role in relation to a nearby settlement.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
developerOfSurroundingArea
Indicates that one entity is responsible for developing, managing, or improving the broader area or environment surrounding another entity.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.