Triple

T6184725
Position Surface form Disambiguated ID Type / Status
Subject Southwest Sabahan languages E138027 entity
Predicate hasCommonAncestryWith P18399 FINISHED
Object other Greater North Borneo 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: other Greater North Borneo languages | Statement: [Southwest Sabahan languages, hasCommonAncestryWith, other Greater North Borneo languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommonAncestryWith
Context triple: [Southwest Sabahan languages, hasCommonAncestryWith, other Greater North Borneo languages]
  • A. hasCommonAncestryGroup
    Indicates that the related entities share membership in the same ancestral or lineage-based group.
  • B. sharesCommonAncestorWith chosen
    Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
  • C. hasAncestor
    Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
  • D. hasCommonRepresentative
    Indicates that two or more entities share the same person or organization acting as their representative.
  • E. hasCommonReference
    Indicates that two or more entities share the same source, citation, or referential basis.
  • 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_69c008a8fd408190b7ec6e42934974a6 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c061020d148190ae2edf2b363f1e24 completed March 22, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69c055fa0a808190bda37832e3ac150c completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:19 p.m.