Triple

T3851551
Position Surface form Disambiguated ID Type / Status
Subject Yeşil Türbe E85304 entity
Predicate lowerLevelUse P44761 FINISHED
Object crypt 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: crypt | Statement: [Yeşil Türbe, lowerLevelUse, crypt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lowerLevelUse
Context triple: [Yeşil Türbe, lowerLevelUse, crypt]
  • A. lowerLevelUsedFor chosen
    Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
  • B. lowestCategory
    Indicates that an entity belongs to the most specific or least general category within a classification hierarchy.
  • C. lowerLocation
    Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
  • D. lowerCourseEnvironment
    Indicates that one course is conducted in a less advanced or less demanding learning environment compared to another course.
  • E. lowerRank
    Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
  • 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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeebd0feb081909cc1d5bf41e4acd6 completed March 9, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69aee750377c8190af70c79768c0edd8 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:19 p.m.