Triple
T2810336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Althing |
E54151
|
entity |
| Predicate | gainedLegislativePowers |
P2844
|
FINISHED |
| Object | 1874 |
—
|
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: 1874 | Statement: [Althing, gainedLegislativePowers, 1874]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedLegislativePowers Context triple: [Althing, gainedLegislativePowers, 1874]
-
A.
hasLegislativePower
chosen
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
B.
transferredLegislativePowerFrom
Indicates that legislative authority or lawmaking power has been moved or delegated from one entity to another.
-
C.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
D.
transferredLegislativePowerTo
Indicates that one entity has formally delegated or handed over its authority to make laws or legislative decisions to another entity.
-
E.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde335b38819090c70d5e2ca14d79 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.