Triple
T31903121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Mumbai attacks |
E814475
|
entity |
| Predicate | policeResponder |
P178336
|
FINISHED |
| Object | Mumbai Police |
—
|
NE NERFINISHED |
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: Mumbai Police | Statement: [2008 Mumbai attacks, policeResponder, Mumbai Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeResponder Context triple: [2008 Mumbai attacks, policeResponder, Mumbai Police]
-
A.
lawEnforcementResponse
Indicates the actions or measures taken by law enforcement agencies in reaction to an incident, behavior, or situation.
-
B.
policeServices
chosen
Indicates that one entity provides or is responsible for law enforcement or policing services to another entity or within a specified area.
-
C.
policeNumber
Indicates that an entity is associated with a specific police-related identification or reference number.
-
D.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
-
E.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, midnight