Triple
T33855109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norsefire regime |
E867750
|
entity |
| Predicate | maintainsPowerBy |
P60897
|
FINISHED |
| Object | terror |
—
|
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: terror | Statement: [Norsefire regime, maintainsPowerBy, terror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsPowerBy Context triple: [Norsefire regime, maintainsPowerBy, terror]
-
A.
maintainsPowerThrough
chosen
Indicates that one entity preserves or secures its authority, control, or dominance by means of another entity or specified mechanism.
-
B.
reservesPowerTo
Indicates that one party retains or explicitly keeps for itself the authority or right to exercise a particular power or function, rather than granting it to others.
-
C.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
D.
modeOfPower
Indicates the type or method of power or energy by which an entity operates or is driven.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:47 a.m.