Triple
T25168298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Dresden-Meissen |
E630242
|
entity |
| Predicate | hasHistoricCathedralCity |
P168022
|
FINISHED |
| Object | Meissen |
—
|
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: Meissen | Statement: [Diocese of Dresden-Meissen, hasHistoricCathedralCity, Meissen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCathedralCity Context triple: [Diocese of Dresden-Meissen, hasHistoricCathedralCity, Meissen]
-
A.
hasCathedralTown
Indicates that a given town is recognized as having a cathedral, typically serving as the seat of a bishop or central church authority.
-
B.
hasCathedralCity
Indicates that a particular city is officially recognized as the cathedral city associated with a given ecclesiastical jurisdiction or region.
-
C.
hasCathedralStatusSince
Indicates the point in time from which something has held the official status of a cathedral.
-
D.
isHistoricalCity
Indicates that a city has historical significance, typically due to its age, past events, or preserved heritage.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 21, 2026, 12:18 p.m.