Triple
T25486813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Burgh of Canongate |
E638731
|
entity |
| Predicate | judicialCentre |
P47029
|
FINISHED |
| Object | Canongate Tolbooth |
—
|
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 Tolbooth | Statement: [Royal Burgh of Canongate, judicialCentre, Canongate Tolbooth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialCentre Context triple: [Royal Burgh of Canongate, judicialCentre, Canongate Tolbooth]
-
A.
courtCenterOf
chosen
Indicates that one entity is the central or primary location (e.g., main venue or focal point) for court-related activities of another entity.
-
B.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
-
C.
courtBasedIn
Indicates that a particular court is located or headquartered in a specified place or jurisdiction.
-
D.
regionalCourt
Indicates that a court operates at a regional level within a larger judicial or administrative system.
-
E.
isCentralJurisdictionOf
Indicates that a jurisdiction serves as the primary or main governing authority for a specified area, system, or set of entities.
- 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_69f5f77d26488190898b7befa111282b |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:32 p.m.