Triple
T32065703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warmia |
E818873
|
entity |
| Predicate | hadSeatOfBishopsAt |
P2276
|
FINISHED |
| Object | Frombork |
—
|
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: Frombork | Statement: [Warmia, hadSeatOfBishopsAt, Frombork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSeatOfBishopsAt Context triple: [Warmia, hadSeatOfBishopsAt, Frombork]
-
A.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
-
B.
isArchdioceseSeatOf
Indicates that a particular archdiocese serves as the central ecclesiastical jurisdiction and administrative seat for a specified church region or authority.
-
C.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
D.
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.
-
E.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b51cc924819080cd8f31a84f4b44 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:22 a.m.