Triple
T30412016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Bruges |
E773645
|
entity |
| Predicate | coversProvince |
P98125
|
FINISHED |
| Object | West Flanders |
—
|
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: West Flanders | Statement: [Diocese of Bruges, coversProvince, West Flanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversProvince Context triple: [Diocese of Bruges, coversProvince, West Flanders]
-
A.
comprisesProvince
Indicates that a larger territorial or administrative unit is made up of, or includes within its boundaries, a specific province.
-
B.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
C.
hasProvinceOrRegion
chosen
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
-
D.
recognizedAsProvinceBy
Indicates that an entity is officially acknowledged or designated as a province by another specified authority or entity.
-
E.
protectedProvince
Indicates that a province is under protection or safeguarding by another entity or authority.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:05 p.m.