Triple
T10445460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Linköping |
E246273
|
entity |
| Predicate | isHistoricDiocese |
P94075
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Diocese of Linköping, isHistoricDiocese, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricDiocese Context triple: [Diocese of Linköping, isHistoricDiocese, true]
-
A.
isHistoricDioceseBishop
Indicates that a person holds or held the office of bishop in a diocese recognized as historic.
-
B.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
-
C.
otherHistoricArchiepiscopalSee
Indicates that an entity has or is associated with another historic archiepiscopal see distinct from its primary one.
-
D.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
-
E.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:16 p.m.