Triple
T28244718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | officeSecularizedInYear |
P194302
|
FINISHED |
| Object | 1803 |
—
|
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: 1803 | Statement: [Prince-Bishop of Lübeck, officeSecularizedInYear, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeSecularizedInYear Context triple: [Prince-Bishop of Lübeck, officeSecularizedInYear, 1803]
-
A.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
B.
foundedInOrBefore
Indicates that the founding of one entity occurred in a specified year or any earlier year.
-
C.
secularAuthorityHeldBy
Indicates that the specified entity holds or exercises non-religious (civil or governmental) authority over another entity.
-
D.
officeReestablishedYear
Indicates the year in which an office or official position was reestablished after having been previously discontinued or abolished.
-
E.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: April 27, 2026, 11 p.m.