Triple
T8996040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Pulheim |
E214912
|
entity |
| Predicate | linguisticEra |
P83770
|
FINISHED |
| Object | Middle Dutch period |
—
|
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 period | Statement: [Bishopric of Pulheim, linguisticEra, Middle Dutch period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticEra Context triple: [Bishopric of Pulheim, linguisticEra, Middle Dutch period]
-
A.
historicalLanguageStage
Indicates that one language variety represents an earlier historical stage or developmental phase of another language.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
-
D.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
E.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68df33c48190a5017426e59c0bc4 |
completed | April 1, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.