Triple

T5566895
Position Surface form Disambiguated ID Type / Status
Subject New Georgia languages E145901 entity
Predicate hasGeneticRelationship P26015 FINISHED
Object close internal genetic relationship 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: close internal genetic relationship | Statement: [New Georgia languages, hasGeneticRelationship, close internal genetic relationship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeneticRelationship
Context triple: [New Georgia languages, hasGeneticRelationship, close internal genetic relationship]
  • A. geneticRelation chosen
    Indicates that two entities are connected through a hereditary or familial genetic relationship.
  • B. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • C. notGeneticallyRelatedTo
    Indicates that there is no genetic or hereditary relationship between the two entities.
  • D. hasMatrilinealConnection
    Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
  • E. sharesDNAWithHumans
    Indicates that one entity possesses genetic material that is evolutionarily related to, and partially identical with, that of humans.
  • 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_69c008fdae24819081aa002ad99cd966 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c02034fc3081908920c52a19d462e1 completed March 22, 2026, 5 p.m.
PD Predicate disambiguation batch_69c01b12826c8190969a584d0f53aa44 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:36 p.m.