Triple

T37177220
Position Surface form Disambiguated ID Type / Status
Subject Amu River E921084 entity
Predicate historicalBoundaryRole P47008 FINISHED
Object cultural boundary in Central Asia 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: cultural boundary in Central Asia | Statement: [Amu River, historicalBoundaryRole, cultural boundary in Central Asia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalBoundaryRole
Context triple: [Amu River, historicalBoundaryRole, cultural boundary in Central Asia]
  • A. historicBoundaryFor chosen
    Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
  • B. eraOfBoundaryRole
    Indicates the historical period or era during which a particular boundary role is defined, active, or relevant.
  • C. hasHistoricalBoundaryChanges
    Indicates that the boundaries of an entity have been altered at some point in its history.
  • D. hasMunicipalityBoundaryRole
    Indicates that an entity participates in or is assigned a specific role related to the boundary of a municipality (such as defining, managing, or being affected by that boundary).
  • E. fareBoundaryRole
    Indicates the specific role an entity plays in defining, managing, or applying a fare boundary within a fare or tariff system.
  • 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_69f76ea16f288190b445aa1604d996f4 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a0186cde2fc819080d7c06503dcc479 completed May 11, 2026, 7:35 a.m.
PD Predicate disambiguation batch_6a0183ff6d34819080c8ad7c11611a36 completed May 11, 2026, 7:23 a.m.
Created at: May 3, 2026, 4:15 p.m.