Triple
T12804250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limelight (New York City nightclub) |
E306101
|
entity |
| Predicate | policeRaids |
P43080
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Limelight (New York City nightclub), policeRaids, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeRaids Context triple: [Limelight (New York City nightclub), policeRaids, 1990s]
-
A.
arrests
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
B.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
C.
policePresence
Indicates that law enforcement officers are present at or monitoring a particular location, event, or situation.
-
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.
lawEnforcementTarget
chosen
Indicates that an entity is the focus or object of attention, investigation, or action by law enforcement authorities.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7e3be48190ba9159c9f1ac2ccd |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.