Triple
T6818331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Düren |
E156827
|
entity |
| Predicate | historicalLanguagePeriod |
P9594
|
FINISHED |
| Object | Middle Ages |
—
|
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 Ages | Statement: [Bishopric of Düren, historicalLanguagePeriod, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguagePeriod Context triple: [Bishopric of Düren, historicalLanguagePeriod, Middle Ages]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
historicalLanguageStage
Indicates that one language variety represents an earlier historical stage or developmental phase of another language.
-
C.
culturalPeriod
chosen
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
D.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
E.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d355b52081909f037cec76bdccf6 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:17 p.m.