Triple
T32133318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thakali language |
E820707
|
entity |
| Predicate | hasDistinctDialects |
P4251
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thakali language, hasDistinctDialects, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctDialects Context triple: [Thakali language, hasDistinctDialects, true]
-
A.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
B.
hasDialects
chosen
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
C.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
D.
hasDialectalDifferenceWith
Indicates that two language varieties differ from each other in dialectal features such as pronunciation, vocabulary, or grammar.
-
E.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in another dialect.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:30 a.m.