Triple
T35011529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falmer |
E1009948
|
entity |
| Predicate | corruptionCause |
P694
|
FINISHED |
| Object | consumption of toxic Dwemer brew |
—
|
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: consumption of toxic Dwemer brew | Statement: [Falmer, corruptionCause, consumption of toxic Dwemer brew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corruptionCause Context triple: [Falmer, corruptionCause, consumption of toxic Dwemer brew]
-
A.
courtCorruption
Indicates that a court or judicial body is involved in corrupt practices, such as bribery, bias, or abuse of legal authority.
-
B.
corruptionLevel
Indicates the degree or extent to which unethical, illegal, or dishonest practices are present or influential in a given context.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
hasCorruptOfficials
Indicates that an entity possesses or is associated with officials who engage in corrupt or unethical behavior.
-
E.
courtCorruptionLevel
Indicates the degree to which a court is affected by corrupt practices or improper influence in its decisions and operations.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.