Triple
T2853946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland Act 2012 |
E63155
|
entity |
| Predicate | expandsPowersInArea |
P1586
|
FINISHED |
| Object | taxation |
—
|
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: taxation | Statement: [Scotland Act 2012, expandsPowersInArea, taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsPowersInArea Context triple: [Scotland Act 2012, expandsPowersInArea, taxation]
-
A.
expandsPowersOf
Indicates that one entity increases, extends, or enhances the authority, capabilities, or influence held by another entity.
-
B.
affectedArea
chosen
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf5f21348190a574fa86bc71c76f |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.