Triple
T29824617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leshy |
E757346
|
entity |
| Predicate | canBeAppeasedBy |
P115823
|
FINISHED |
| Object | offerings |
—
|
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: offerings | Statement: [Leshy, canBeAppeasedBy, offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAppeasedBy Context triple: [Leshy, canBeAppeasedBy, offerings]
-
A.
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.
-
B.
canBeTamedWith
Indicates that an entity can be domesticated, controlled, or made docile through the use of a specified tool, method, or resource.
-
C.
wasPacifiedBy
chosen
Indicates that an entity became calm, subdued, or brought under control as a result of the actions or influence of another entity.
-
D.
canBeSubduedBy
Indicates that one entity is capable of overpowering, restraining, or otherwise bringing another entity under control.
-
E.
appeases
Indicates an action where one entity calms, placates, or satisfies another entity to reduce anger, tension, or hostility.
- 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_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 29, 2026, 5:31 p.m.