Triple
T9766205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Dormagen |
E236996
|
entity |
| Predicate | usedLanguageForChancery |
P30358
|
FINISHED |
| Object | Middle Dutch |
—
|
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: Middle Dutch | Statement: [Bishopric of Dormagen, usedLanguageForChancery, Middle Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLanguageForChancery Context triple: [Bishopric of Dormagen, usedLanguageForChancery, Middle Dutch]
-
A.
hasChancery
Indicates that an entity possesses or is associated with a chancery, i.e., an official office or administrative body responsible for formal documents and records.
-
B.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
C.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
D.
languageOfPromulgation
Indicates the language in which a law, decree, or official act is formally issued or proclaimed.
-
E.
languageOfTreatyAftermath
Indicates the language used in documents, discourse, or arrangements that arise as a consequence of a treaty’s implementation or aftermath.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a15e408190909745cb1c30937d |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.