Triple
T13002964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government (Scotland) Act 1973 |
E322214
|
entity |
| Predicate | createdTier |
P64281
|
FINISHED |
| Object | regions |
—
|
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: regions | Statement: [Local Government (Scotland) Act 1973, createdTier, regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdTier Context triple: [Local Government (Scotland) Act 1973, createdTier, regions]
-
A.
createdEntityType
chosen
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
B.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
C.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
D.
createdUnder
Indicates that something was created during the time period or within the authority, rules, or conditions defined by another entity or context.
-
E.
createdLevelOfCourt
Indicates that an entity (such as a person, body, or law) is responsible for establishing or bringing into existence a particular level within a court system.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9a2a448190968833354280e474 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:47 p.m.