Triple
T8738784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil–Irula subgroup |
E207451
|
entity |
| Predicate | hasLinguisticVariety |
P84576
|
FINISHED |
| Object | Tamil |
—
|
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: Tamil | Statement: [Tamil–Irula subgroup, hasLinguisticVariety, Tamil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticVariety Context triple: [Tamil–Irula subgroup, hasLinguisticVariety, Tamil]
-
A.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
B.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
C.
partOfLinguisticVariety
Indicates that one linguistic variety (such as a dialect, register, or style) is a constituent or subset of another, broader linguistic variety.
-
D.
primaryLanguageVariety
Indicates the main dialect or specific variety of a language that an entity primarily uses.
-
E.
hasLinguisticDomain
Indicates that something (such as a term, expression, or resource) is associated with or applies within a particular linguistic domain or language context.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d470c8c81909ead395ef704c6ba |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:38 p.m.