Triple
T5849065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Frisian |
E129982
|
entity |
| Predicate | hasNumberOfDialects |
P66705
|
FINISHED |
| Object | 10+ |
—
|
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: 10+ | Statement: [North Frisian, hasNumberOfDialects, 10+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfDialects Context triple: [North Frisian, hasNumberOfDialects, 10+]
-
A.
hasDialects
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
B.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
C.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
D.
hasTraditionalDialect
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
-
E.
hasMajorDialectGroup
Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
- F. None of above. chosen
Provenance (4 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c03c8d579081909d7b97fc9014b5d7 |
completed | March 22, 2026, 7:01 p.m. |
Created at: March 22, 2026, 3:55 p.m.