Triple
T23684284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian nobility |
E585119
|
entity |
| Predicate | abolishedPrivilegesBy |
P111458
|
FINISHED |
| Object | Storting |
—
|
NE NERFINISHED |
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: Storting | Statement: [Norwegian nobility, abolishedPrivilegesBy, Storting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedPrivilegesBy Context triple: [Norwegian nobility, abolishedPrivilegesBy, Storting]
-
A.
formerPrivilege
Indicates that an entity once held a certain privilege or right but no longer does so in the present.
-
B.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
C.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
D.
canBeAbolishedBy
chosen
Indicates that one entity has the authority or power to formally end, revoke, or eliminate another entity.
-
E.
previouslyAbolished
Indicates that something was officially ended, discontinued, or annulled at some point in the past.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4fb26c88190a6776e4dfd10d54c |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.