Triple
T10722354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvera |
E252853
|
entity |
| Predicate | extorts |
P33834
|
FINISHED |
| Object | Mexican farming village |
—
|
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: Mexican farming village | Statement: [Calvera, extorts, Mexican farming village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extorts Context triple: [Calvera, extorts, Mexican farming village]
-
A.
persecutes
Indicates that one entity persistently harasses, oppresses, or inflicts suffering on another, often in an unjust or hostile manner.
-
B.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
-
C.
exploits
chosen
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
D.
blackmails
Indicates that one entity coerces another by threatening to reveal damaging or sensitive information unless specific demands are met.
-
E.
blackmailedFor
Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d44d0048190a78aae2357e864a5 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.