Triple
T11599429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Hemer |
E275088
|
entity |
| Predicate | usedInLegalDocuments |
P5304
|
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 Hemer, usedInLegalDocuments, Middle Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLegalDocuments Context triple: [Bishopric of Hemer, usedInLegalDocuments, Middle Dutch]
-
A.
usedLegalInstrument
Indicates that one party employed or relied upon a specific legal instrument (such as a contract, statute, or court order) in the context of an action or relationship with another party.
-
B.
usedInLegalCitation
Indicates that one entity is referenced or relied upon as an authoritative source within a legal citation to support legal arguments or decisions.
-
C.
usedInFinancialDocuments
Indicates that something is employed or appears within financial documents or records.
-
D.
legalTermUsedFrom
Indicates that a particular legal term has been in official or recognized use starting from a specified point in time.
-
E.
usedInOfficialDocumentsOf
chosen
Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity or 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8954c3c248190bcccd4c7ff667b3a |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.