Triple

T25521880
Position Surface form Disambiguated ID Type / Status
Subject Road to Palios E639671 entity
Predicate hasInfluenceRegion P19397 FINISHED
Object Balkans 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: Balkans | Statement: [Road to Palios, hasInfluenceRegion, Balkans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfluenceRegion
Context triple: [Road to Palios, hasInfluenceRegion, Balkans]
  • A. hasRegionalInfluenceFrom
    Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
  • B. influencesRegion chosen
    Indicates that one entity has an effect on, shapes, or alters the conditions, characteristics, or behavior of a specified region.
  • C. hasInfluenceScope
    Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
  • D. mainTerritoryOfInfluence
    Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
  • E. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • 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_69e75dbe32e48190a62d749a0ff2a96a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 21, 2026, 3:01 p.m.