Triple

T636497
Position Surface form Disambiguated ID Type / Status
Subject Balkan Turkish E16632 entity
Predicate typologicalArea P1968 FINISHED
Object Balkan linguistic area 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: Balkan linguistic area | Statement: [Balkan Turkish, typologicalArea, Balkan linguistic area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typologicalArea
Context triple: [Balkan Turkish, typologicalArea, Balkan linguistic area]
  • A. regionType
    Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
  • B. culturalRegion chosen
    Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
  • C. demographicRegion
    Indicates that an entity is associated with, belongs to, or is characterized by a particular geographic or administrative region for demographic purposes.
  • D. traditionalTerritorialDesignation
    Indicates a historically or culturally recognized claim or assignment of a geographic area to a particular group, authority, or identity.
  • E. typology
    Indicates a classification relationship in which entities are grouped or organized according to shared types, patterns, or structural characteristics.
  • 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_69a4936be1c88190af56540324b57da7 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49ee7fdbc8190858e42bb1bfdb3ff completed March 1, 2026, 8:17 p.m.
PD Predicate disambiguation batch_69a49d0483908190a5ec42a7403c258e completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.