Triple
T3670737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatki |
E77871
|
entity |
| Predicate | ISO639Family |
P35117
|
FINISHED |
| Object | Indo-European languages |
—
|
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: Indo-European languages | Statement: [Jatki, ISO639Family, Indo-European languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639Family Context triple: [Jatki, ISO639Family, Indo-European languages]
-
A.
ISO639FamilyGrouping
Indicates that languages are grouped together according to their ISO 639-defined language family or subfamily classification.
-
B.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
C.
languageFamilyOf
chosen
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
D.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
E.
languageFamilyAssociation
Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42c96648190abbd5d23b25d6a6b |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.