Triple
T36505434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Empire |
E899446
|
entity |
| Predicate | oppressiveTo |
P20070
|
FINISHED |
| Object | non-human species |
—
|
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: non-human species | Statement: [Galactic Empire, oppressiveTo, non-human species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppressiveTo Context triple: [Galactic Empire, oppressiveTo, non-human species]
-
A.
hasOppressor
Indicates that one entity acts as an oppressor toward another, exerting unjust or abusive power or control over them.
-
B.
isTyrannical
Indicates that an entity exercises power or authority in an oppressive, cruel, or unjustly authoritarian manner over others.
-
C.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
-
D.
hasOppressiveInstitutionalRole
Indicates that an entity occupies or embodies a position within an institution that systematically enforces or perpetuates oppression or unjust power relations.
-
E.
persecutes
chosen
Indicates that one entity persistently harasses, oppresses, or inflicts suffering on another, often in an unjust or hostile manner.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.