Triple
T14669910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electorate of Trier |
E344481
|
entity |
| Predicate | archbishopricFounded |
P80794
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Electorate of Trier, archbishopricFounded, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archbishopricFounded Context triple: [Electorate of Trier, archbishopricFounded, 3rd century]
-
A.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
-
B.
archbishopricSeatPeriod
chosen
Indicates the time period during which a particular location served as the official seat of an archbishopric.
-
C.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
D.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
-
E.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.