Triple
T5454890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abe Reles became a government informant |
E122454
|
entity |
| Predicate | connectedToSubsequentEvent |
P54905
|
FINISHED |
| Object | mysterious death of Abe Reles in police custody |
—
|
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: mysterious death of Abe Reles in police custody | Statement: [Abe Reles became a government informant, connectedToSubsequentEvent, mysterious death of Abe Reles in police custody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToSubsequentEvent Context triple: [Abe Reles became a government informant, connectedToSubsequentEvent, mysterious death of Abe Reles in police custody]
-
A.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
B.
laterRelatedEvent
chosen
Indicates that one event is temporally related to another by occurring at a later time.
-
C.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
D.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
E.
subsequentEntity
Indicates that one entity occurs or appears after another entity in a sequence or ordered arrangement.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.