Triple
T29824580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domovoi |
E757345
|
entity |
| Predicate | behaviorTowardDisrespect |
P101476
|
FINISHED |
| Object | causes disturbances |
—
|
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: causes disturbances | Statement: [Domovoi, behaviorTowardDisrespect, causes disturbances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorTowardDisrespect Context triple: [Domovoi, behaviorTowardDisrespect, causes disturbances]
-
A.
disrespect
Indicates a relationship in which one entity shows a lack of respect, regard, or consideration toward another.
-
B.
侮辱行為の扱い
Indicates the handling or treatment of acts of insult or abusive behavior between entities.
-
C.
attitudeTowardOthers
Indicates the nature or disposition of one entity’s feelings, judgments, or behavioral stance toward other entities.
-
D.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
E.
aggressiveness
chosen
Indicates a tendency or disposition of an entity to initiate hostile, forceful, or confrontational actions toward others.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67596b610819088e85360aafa860c |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:31 p.m.