Triple
T26253092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John’s Episcopal Church, Princes Street, Edinburgh |
E656647
|
entity |
| Predicate | holdsRegularServices |
P65303
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [St John’s Episcopal Church, Princes Street, Edinburgh, holdsRegularServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsRegularServices Context triple: [St John’s Episcopal Church, Princes Street, Edinburgh, holdsRegularServices, yes]
-
A.
hasServiceStandard
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
-
B.
hasRegularServicePattern
chosen
Indicates that an entity consistently follows a defined, recurring schedule or pattern of service over time.
-
C.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
D.
holdsService
Indicates that one entity provides, maintains, or is responsible for a particular service for another entity or context.
-
E.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcc29cc81908880bd825cb12141 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 9:07 p.m.