Triple
T33042184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leominster District Council |
E845496
|
entity |
| Predicate | hasGovernmentOfficeLocation |
P88614
|
FINISHED |
| Object | Leominster |
—
|
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: Leominster | Statement: [Leominster District Council, hasGovernmentOfficeLocation, Leominster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentOfficeLocation Context triple: [Leominster District Council, hasGovernmentOfficeLocation, Leominster]
-
A.
hasDistrictOfficeLocation
Indicates that an entity’s district office is located at a specified place or address.
-
B.
locationOfGoverningBody
chosen
Indicates the place where a governing body is based or carries out its official functions.
-
C.
headquartersOfOffice
Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
-
D.
fieldOfficesLocation
Indicates the geographical location where an organization's field offices are situated or based.
-
E.
locatedInTheGovernmentBuilding
Indicates that one entity is situated within or inside a government-owned or government-operated building.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:24 a.m.