Triple
T1461488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Peachum |
E31520
|
entity |
| Predicate | turnsIn |
P29045
|
FINISHED |
| Object | his own criminal associates |
—
|
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: his own criminal associates | Statement: [Mr. Peachum, turnsIn, his own criminal associates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnsIn Context triple: [Mr. Peachum, turnsIn, his own criminal associates]
-
A.
turns
Indicates a change in orientation, direction, or state initiated by one entity affecting itself or another entity.
-
B.
turningPointIn
Indicates that an event or situation serves as a decisive change or pivotal moment within a larger process, narrative, or development.
-
C.
turnedPro
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
-
D.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
E.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59ecb60819082217b034e18381f |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.