Triple
T33862197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish devolution |
E867952
|
entity |
| Predicate | policyAreaReserved |
P73047
|
FINISHED |
| Object | foreign affairs |
—
|
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: foreign affairs | Statement: [Scottish devolution, policyAreaReserved, foreign affairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyAreaReserved Context triple: [Scottish devolution, policyAreaReserved, foreign affairs]
-
A.
policyAreasReservedToCentralState
chosen
Indicates that certain policy areas are exclusively assigned to and controlled by the central state, not by regional or local authorities.
-
B.
policyAreaScope
Indicates the specific policy domain or thematic area to which an action, decision, or measure is relevant or applies.
-
C.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
D.
coordinatesPolicyAreas
Indicates that one entity organizes and aligns activities or strategies across multiple policy areas involving another entity.
-
E.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:47 a.m.