Triple
T3121161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Lucas |
E65185
|
entity |
| Predicate | reArrestedFor |
P15395
|
FINISHED |
| Object | drug-related charges in the 1980s |
—
|
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: drug-related charges in the 1980s | Statement: [Frank Lucas, reArrestedFor, drug-related charges in the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reArrestedFor Context triple: [Frank Lucas, reArrestedFor, drug-related charges in the 1980s]
-
A.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
B.
arrestedFor
chosen
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
C.
arrests
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
D.
numberOfArrests
Indicates the count of times an entity has been arrested.
-
E.
arrestedAt
Indicates that an entity was apprehended or taken into custody at a specific location or during a specific event or time.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5295cd481908d52e165538c67fa |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.