Triple
T25486758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirk Session of Canongate |
E638730
|
entity |
| Predicate | governsBuilding |
P760
|
FINISHED |
| Object | Canongate Kirk |
—
|
NE NERFINISHED |
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: Canongate Kirk | Statement: [Kirk Session of Canongate, governsBuilding, Canongate Kirk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsBuilding Context triple: [Kirk Session of Canongate, governsBuilding, Canongate Kirk]
-
A.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
B.
hasGovernmentBuildingType
Indicates that a government building is classified as having a specific type or category of governmental function or use.
-
C.
servesMunicipalBuilding
Indicates that an entity provides services or functions in support of a municipal (city or local government) building.
-
D.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
isBuildingOf
Indicates that one entity is a building that belongs to, houses, or is associated with another entity (such as an organization, institution, or complex).
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 21, 2026, 2:32 p.m.