Triple
T31103821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Harkonnen |
E792741
|
entity |
| Predicate | treatmentOfSubjects |
P172949
|
FINISHED |
| Object | brutal |
—
|
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: brutal | Statement: [House Harkonnen, treatmentOfSubjects, brutal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentOfSubjects Context triple: [House Harkonnen, treatmentOfSubjects, brutal]
-
A.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
B.
treatmentOf
Indicates a relationship where one entity administers, provides, or is responsible for a therapeutic intervention directed toward another entity (typically a patient or condition).
-
C.
subjectTreatment
Indicates that a subject is receiving, undergoing, or being administered a particular treatment or therapeutic intervention.
-
D.
isSubjectOfStudy
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
-
E.
subjectGroup
Indicates that an entity functions as a group or collection that the subject belongs to or is categorized under.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 29, 2026, 9:03 p.m.