Triple
T14438694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biertan Fortified Church |
E358032
|
entity |
| Predicate | seatOfBishopricTo |
P2276
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [Biertan Fortified Church, seatOfBishopricTo, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatOfBishopricTo Context triple: [Biertan Fortified Church, seatOfBishopricTo, 1867]
-
A.
episcopalSeeOf
chosen
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
B.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
-
C.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
D.
isArchdioceseSeatOf
Indicates that a particular archdiocese serves as the central ecclesiastical jurisdiction and administrative seat for a specified church region or authority.
-
E.
isTitularChurchOf
Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914a45ec81909ab8ccf302047d7f |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.