Triple
T29530976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury parish |
E749200
|
entity |
| Predicate | hasBuildingAtItsCentre |
P126713
|
FINISHED |
| Object | Bury Parish Church |
E205584
|
NE 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: Bury Parish Church | Statement: [Bury parish, hasBuildingAtItsCentre, Bury Parish Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingAtItsCentre Context triple: [Bury parish, hasBuildingAtItsCentre, Bury Parish Church]
-
A.
hasMonumentInCenter
chosen
Indicates that a place or area has a monument located at its central point or main focal area.
-
B.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
C.
hasMainEdifice
Indicates that an entity possesses or is associated with a primary or principal building or structure.
-
D.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
E.
hasHeadquartersBuilding
Indicates that an organization possesses a specific building that serves as its headquarters location.
- F. None of above.
Provenance (4 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2661549654819094c29a40b79e697c |
completed | June 8, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 4:52 p.m.