Triple
T29824579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domovoi |
E757345
|
entity |
| Predicate | behaviorTowardLazyPeople |
P168187
|
FINISHED |
| Object | plays tricks |
—
|
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: plays tricks | Statement: [Domovoi, behaviorTowardLazyPeople, plays tricks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorTowardLazyPeople Context triple: [Domovoi, behaviorTowardLazyPeople, plays tricks]
-
A.
behaviorTowardDiligentPeople
Indicates how an entity acts, responds, or conducts itself specifically in relation to people who are diligent.
-
B.
workBehavior
Indicates how an entity typically acts, performs, or conducts itself in a work or professional context.
-
C.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
D.
privateBehavior
Indicates behavior or actions that are intended to be kept confidential, hidden, or restricted from public or general observation.
-
E.
typicallyLack
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
- 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_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_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:31 p.m.