Triple
T27148259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bow Street, London |
E682010
|
entity |
| Predicate | policingInstitutionAssociated |
P119631
|
FINISHED |
| Object | Bow Street Runners |
—
|
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: Bow Street Runners | Statement: [Bow Street, London, policingInstitutionAssociated, Bow Street Runners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policingInstitutionAssociated Context triple: [Bow Street, London, policingInstitutionAssociated, Bow Street Runners]
-
A.
hasPoliceInstitution
Indicates that an entity is associated with, governed by, or served by a particular police institution or law enforcement body.
-
B.
lawEnforcementOrganization
Indicates that the subject is an organization whose primary role is to enforce laws and maintain public order.
-
C.
associatedWithLawEnforcementAgency
chosen
Indicates that an entity has a formal connection, role, or involvement with a law enforcement agency.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:12 a.m.