Triple
T9380351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presbytery of Glasgow |
E225765
|
entity |
| Predicate | hasPolityLevel |
P1085
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Presbytery of Glasgow, hasPolityLevel, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolityLevel Context triple: [Presbytery of Glasgow, hasPolityLevel, regional]
-
A.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
B.
hasMunicipalLevel
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
-
C.
governingBodyLevel
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
-
D.
levelOfGovernment
chosen
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
E.
hasFormOfTerritorialOrganization
Indicates that one entity possesses or is structured according to a particular type or form of territorial organization.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bc94108190a1b8146a78166009 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.