Triple
T2101591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkic languages |
E37102
|
entity |
| Predicate | areNotGeneticallyRelatedTo |
P8167
|
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: [Turkic languages, areNotGeneticallyRelatedTo, Indo-European languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areNotGeneticallyRelatedTo Context triple: [Turkic languages, areNotGeneticallyRelatedTo, Indo-European languages]
-
A.
notGeneticallyRelatedTo
chosen
Indicates that there is no genetic or hereditary relationship between the two entities.
-
B.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
C.
moreDistantlyRelatedTo
Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.