Triple
T4966697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Bodkin Adams |
E111543
|
entity |
| Predicate | suspectedVictimsCount |
P41344
|
FINISHED |
| Object | over 160 patients |
—
|
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: over 160 patients | Statement: [John Bodkin Adams, suspectedVictimsCount, over 160 patients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspectedVictimsCount Context triple: [John Bodkin Adams, suspectedVictimsCount, over 160 patients]
-
A.
numberOfSuspectedVictims
chosen
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
-
B.
estimatedVictimsUnderAuthority
Indicates that a specified authority is estimated to have a certain number of victims under its control, influence, or jurisdiction.
-
C.
numberOfVictimsClaimedInTestimony
Indicates the quantity of victims that a person asserts or reports in their testimony.
-
D.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
E.
hasVictims
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.