Triple
T34982078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trabe |
E1008840
|
entity |
| Predicate | treatmentOfKazon |
P182166
|
FINISHED |
| Object | oppressive |
—
|
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: oppressive | Statement: [Trabe, treatmentOfKazon, oppressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentOfKazon Context triple: [Trabe, treatmentOfKazon, oppressive]
-
A.
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).
-
B.
treatsKarnaAs
Indicates how one entity behaves toward or regards Karna, characterizing the nature or quality of their treatment of him.
-
C.
KaumodakiOf
Indicates that one entity is the Kaumodaki (the specific mace/weapon) associated with, possessed by, or emblematic of another entity.
-
D.
Juyo
Indicates a relationship where one entity is associated with or characterized by the concept or style referred to as "Juyo."
-
E.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.