Triple

T1173276
Position Surface form Disambiguated ID Type / Status
Subject Japonic languages E24960 entity
Predicate possibleRelationTo P10690 FINISHED
Object Koreanic languages (hypothetical) 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: Koreanic languages (hypothetical) | Statement: [Japonic languages, possibleRelationTo, Koreanic languages (hypothetical)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleRelationTo
Context triple: [Japonic languages, possibleRelationTo, Koreanic languages (hypothetical)]
  • A. relationshipType chosen
    Indicates the specific kind of relationship that exists between two or more entities.
  • B. relationshipToHumans
    Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
  • C. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • D. moreDistantlyRelatedTo
    Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
  • E. historicalRelationship
    Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcecab688190b21a926874cd98d1 completed March 1, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69a4bb5656948190b0b1d5446ad06005 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.