Triple
T21681670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khlestakov |
E535121
|
entity |
| Predicate | receivesFromOthers |
P52361
|
FINISHED |
| Object | bribes |
—
|
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: bribes | Statement: [Khlestakov, receivesFromOthers, bribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesFromOthers Context triple: [Khlestakov, receivesFromOthers, bribes]
-
A.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
receivesShareOf
Indicates that one entity is allocated or obtains a portion of something (such as profits, resources, or ownership) that is divided among multiple parties.
-
C.
hearsFrom
Indicates that one entity receives information, communication, or a message from another entity.
-
D.
receivesLivingFrom
Indicates that one entity obtains or is given a living organism or life-sustaining resource from another entity.
-
E.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c69990819088a1134ecea09099 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.