Triple
T1232305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Lichfield |
E26468
|
entity |
| Predicate | metropolitanStatusHeld |
P24765
|
FINISHED |
| Object | 787–803 |
—
|
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: 787–803 | Statement: [Diocese of Lichfield, metropolitanStatusHeld, 787–803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metropolitanStatusHeld Context triple: [Diocese of Lichfield, metropolitanStatusHeld, 787–803]
-
A.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
B.
hasMetropolitanAuthorityOver
Indicates that one entity holds official governing or administrative authority over a metropolitan area or region associated with another entity.
-
C.
hasMetropolitanCounty
Indicates that an entity is associated with, located within, or administered by a specific metropolitan county.
-
D.
hasMetropolitanAreaName
Indicates that an entity is associated with a metropolitan area identified by a specific name.
-
E.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
- F. None of above. chosen
Provenance (4 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5b40208190b115a6a344402caf |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.