Triple
T20515549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Government and Scottish Government |
E503673
|
entity |
| Predicate | shareResponsibilityFor |
P56398
|
FINISHED |
| Object | governance of Scotland |
—
|
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: governance of Scotland | Statement: [UK Government and Scottish Government, shareResponsibilityFor, governance of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareResponsibilityFor Context triple: [UK Government and Scottish Government, shareResponsibilityFor, governance of Scotland]
-
A.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
hasResponsibilitiesSharedWith
chosen
Indicates that two or more entities share joint responsibility for certain tasks, duties, or obligations.
-
C.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
D.
sharesRoleWith
Indicates that two entities hold the same role or position within a given context or system.
-
E.
sharesMission
Indicates that two or more entities are aligned in purpose, pursuing the same overarching mission or goal.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f41eee481908121e54c7bd691ca |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.