Triple

T26849552
Position Surface form Disambiguated ID Type / Status
Subject Bizans Müesseselerinin Osmanlı Müesseselerine Tesiri E676020 entity
Predicate bölgeselOdak P2160 FINISHED
Object Balkanlar NE NERFINISHED

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: Balkanlar | Statement: [Bizans Müesseselerinin Osmanlı Müesseselerine Tesiri, bölgeselOdak, Balkanlar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bölgeselOdak
Context triple: [Bizans Müesseselerinin Osmanlı Müesseselerine Tesiri, bölgeselOdak, Balkanlar]
  • A. zone chosen
    Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
  • B. region1
    Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
  • C. basinDistrict
    Indicates a relationship where an administrative or geographic district is associated with, or falls within, a particular drainage or river basin.
  • D. arealRegion
    Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
  • E. regionGuided
    Indicates that one entity directs, controls, or influences the behavior or development of another within a specific geographic or conceptual region.
  • 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_69eee9b9d7708190a15d7485709ae981 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6383625cc8190aa223d8ef655743c completed May 2, 2026, 5:45 p.m.
PD Predicate disambiguation batch_69f63709e4848190b5cf322e06b23fb6 completed May 2, 2026, 5:40 p.m.
Created at: April 27, 2026, 5:15 a.m.