Triple
T30855198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Havelberg |
E785899
|
entity |
| Predicate | hadChapter |
P164747
|
FINISHED |
| Object | Cathedral chapter of Havelberg |
—
|
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: Cathedral chapter of Havelberg | Statement: [Bishopric of Havelberg, hadChapter, Cathedral chapter of Havelberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChapter Context triple: [Bishopric of Havelberg, hadChapter, Cathedral chapter of Havelberg]
-
A.
hadChapterOf
Indicates that an entity (such as a book or document) includes or contains a specific chapter as one of its parts.
-
B.
hadChapterAt
chosen
Indicates that an organization or group maintained an official chapter, branch, or local unit at a specified location or institution.
-
C.
hasGeneralChapter
Indicates that an entity is associated with, or contains, a general chapter (a broad or overarching section) within a larger structured document or framework.
-
D.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
E.
chapterAfter
Indicates that one chapter directly follows another in a sequential ordering.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917f924481909449b790ae38a271 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.