Triple
T34109018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedfordshire Police |
E874785
|
entity |
| Predicate | policesFacility |
P119294
|
FINISHED |
| Object | London Luton Airport |
—
|
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: London Luton Airport | Statement: [Bedfordshire Police, policesFacility, London Luton Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policesFacility Context triple: [Bedfordshire Police, policesFacility, London Luton Airport]
-
A.
nearLawEnforcementFacility
Indicates that one entity is located in close physical proximity to a law enforcement facility, such as a police station or similar agency location.
-
B.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
C.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
hasPoliceInstitution
chosen
Indicates that an entity is associated with, governed by, or served by a particular police institution or law enforcement body.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:53 a.m.