Triple

T5816236
Position Surface form Disambiguated ID Type / Status
Subject Tunca Bridge E128992 entity
Predicate hasRegionImportance P12510 FINISHED
Object important crossing over Tunca River in Edirne 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: important crossing over Tunca River in Edirne | Statement: [Tunca Bridge, hasRegionImportance, important crossing over Tunca River in Edirne]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionImportance
Context triple: [Tunca Bridge, hasRegionImportance, important crossing over Tunca River in Edirne]
  • A. hasRegionalSignificance chosen
    Indicates that something holds particular importance, influence, or relevance within a specific geographic region.
  • B. peakImportance
    Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
  • C. relativeImportanceInCountry
    Indicates the comparative significance or priority of something within the context of a specific country.
  • D. impactRegion
    Indicates the geographic or spatial area that is affected or influenced by a particular event, action, or phenomenon.
  • E. isImportantFor
    Indicates that something holds significant value, relevance, or necessity in relation to something else.
  • 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_69c0084869e881908d7859492183ca7b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0400f1af881908d376ea4793f6dea completed March 22, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69c0333fdd7081908d829265caa2ac11 completed March 22, 2026, 6:21 p.m.
Created at: March 22, 2026, 3:53 p.m.