Triple
T37121038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niederrheinisches Platt |
E919251
|
entity |
| Predicate | isLinguisticallyCloseTo |
P147965
|
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: [Niederrheinisches Platt, isLinguisticallyCloseTo, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinguisticallyCloseTo Context triple: [Niederrheinisches Platt, isLinguisticallyCloseTo, Dutch]
-
A.
hasLanguageSimilarTo
chosen
Indicates that one entity uses or is associated with a language that is similar or closely related to the language used or associated with another entity.
-
B.
hasLexicalSimilarityWith
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
-
C.
hasPhonologicalSimilarityTo
Indicates that two linguistic elements share similar sound patterns or phonological features.
-
D.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
E.
hasGrammaticalSimilarityTo
Indicates that two linguistic elements share similar grammatical structure, form, or function.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.