Triple

T32046097
Position Surface form Disambiguated ID Type / Status
Subject Sari, Kerman E818354 entity
Predicate hasRegionalLocation P203671 FINISHED
Object southeast of Iran 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: southeast of Iran | Statement: [Sari, Kerman, hasRegionalLocation, southeast of Iran]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionalLocation
Context triple: [Sari, Kerman, hasRegionalLocation, southeast of Iran]
  • A. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • B. hasRegionalPosition
    Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
  • C. hasRegionalEntity
    Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
  • D. isRegional
    Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
  • E. hasRegionalProfile
    Indicates that an entity is associated with or characterized by a specific regional profile or set of region-based attributes.
  • F. None of above. chosen

Provenance (4 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_69f348fcfb648190859f6be5e04b7cfe completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a01c41dfe248190a68f4a262591b30f completed May 11, 2026, 11:57 a.m.
PD Predicate disambiguation batch_6a01c375d14c8190a15bfa12623588a9 completed May 11, 2026, 11:54 a.m.
PDg Predicate description generation batch_6a01c41d38608190923c5fd32a59b865 completed May 11, 2026, 11:57 a.m.
Created at: May 1, 2026, 12:20 a.m.