Triple
T22342989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rap Back Service |
E552321
|
entity |
| Predicate | notifiesAbout |
P119861
|
FINISHED |
| Object | subsequent arrests |
—
|
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: subsequent arrests | Statement: [Rap Back Service, notifiesAbout, subsequent arrests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notifiesAbout Context triple: [Rap Back Service, notifiesAbout, subsequent arrests]
-
A.
notification
Indicates that one entity sends or presents an alert or message to another entity to inform them of some event, change, or required action.
-
B.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
C.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
D.
announcedInCase
Indicates that a particular announcement or declaration was made within the context of a specific case or legal proceeding.
-
E.
providesAlertsTo
chosen
Indicates that one entity sends or delivers alerts or notifications to another entity.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15795b2a881908d6cb8f97443ca17 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.