Triple
T31452083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diederich Heßling |
E802349
|
entity |
| Predicate | treatsSubordinates |
P174852
|
FINISHED |
| Object | with despotism |
—
|
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: with despotism | Statement: [Diederich Heßling, treatsSubordinates, with despotism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsSubordinates Context triple: [Diederich Heßling, treatsSubordinates, with despotism]
-
A.
treatsSuperiors
Indicates how an entity behaves toward or interacts with those in higher-ranking or superior positions.
-
B.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
C.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
-
D.
supervisesBy
Indicates that one entity is overseen, directed, or managed under the authority of another entity.
-
E.
underDirectAuthorityOf
Indicates that one entity is directly controlled, supervised, or governed by another entity with no intermediary authority in between.
- F. None of above. chosen
Provenance (4 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: April 30, 2026, 9:14 p.m.