Triple
T29824744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kikimora |
E757348
|
entity |
| Predicate | appeasesWith |
P70511
|
FINISHED |
| Object | tidy household |
—
|
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: tidy household | Statement: [Kikimora, appeasesWith, tidy household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appeasesWith Context triple: [Kikimora, appeasesWith, tidy household]
-
A.
appeases
chosen
Indicates an action where one entity calms, placates, or satisfies another entity to reduce anger, tension, or hostility.
-
B.
propitiatedFor
Indicates that one entity has taken action to appease, atone to, or gain favor from another entity on behalf of a specific person, group, or cause.
-
C.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
D.
pleaTo
Indicates that one entity formally requests or appeals to another entity, often seeking a specific decision, action, or lenient judgment.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 5:31 p.m.