Triple
T31956161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Astorga |
E815910
|
entity |
| Predicate | notableCityInDiocese |
P41762
|
FINISHED |
| Object | Ponferrada |
E879350
|
NE 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: Ponferrada | Statement: [Diocese of Astorga, notableCityInDiocese, Ponferrada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCityInDiocese Context triple: [Diocese of Astorga, notableCityInDiocese, Ponferrada]
-
A.
isArchdioceseSeatOf
Indicates that a particular archdiocese serves as the central ecclesiastical jurisdiction and administrative seat for a specified church region or authority.
-
B.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
-
C.
notableCityIncluded
chosen
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
D.
notableBishop
Indicates that a person holds or held the position of bishop and is recognized as particularly significant or distinguished in that role.
-
E.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
- F. None of above.
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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a349e97db348190bb3e0e2aae4617fd |
completed | June 19, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:08 a.m.