Triple
T3699937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Limburg |
E78551
|
entity |
| Predicate | traditionalLanguageForm |
P6281
|
FINISHED |
| Object | 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: Dutch | Statement: [Duchess of Limburg, traditionalLanguageForm, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLanguageForm Context triple: [Duchess of Limburg, traditionalLanguageForm, Dutch]
-
A.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
B.
languageForm
chosen
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
C.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
D.
governingLanguageTradition
Indicates that one language tradition holds authoritative or regulatory influence over another in terms of norms, standards, or accepted practices.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc513d26c8190bfdf25f62af8c6ca |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.