Triple
T15171755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conversion of Iceland at the Althing |
E362502
|
entity |
| Predicate | decisionCharacter |
P2165
|
FINISHED |
| Object | peaceful settlement |
—
|
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: peaceful settlement | Statement: [conversion of Iceland at the Althing, decisionCharacter, peaceful settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionCharacter Context triple: [conversion of Iceland at the Althing, decisionCharacter, peaceful settlement]
-
A.
decisionMakingRole
Indicates that an entity holds responsibility or authority in making decisions for or on behalf of another entity or group.
-
B.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
C.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
decisionEffect
Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
-
E.
decisionRole
Indicates that an entity participates in a decision-making process with a specified role or function in that decision.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064ec56481909f11fa6e5686f076 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.