Triple

T37416740
Position Surface form Disambiguated ID Type / Status
Subject Secteur fortifié du Dauphiné E929728 entity
Predicate borderDefenseLineOf P66390 FINISHED
Object France 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: France | Statement: [Secteur fortifié du Dauphiné, borderDefenseLineOf, France]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderDefenseLineOf
Context triple: [Secteur fortifié du Dauphiné, borderDefenseLineOf, France]
  • A. partOfDefenseLine chosen
    Indicates that one entity functions as a component or segment within the overall defensive formation or system of another entity.
  • B. borderDemarcationRelatedTo
    Indicates a relationship between a border demarcation and another entity, such as a process, document, event, or feature, that is relevant to defining, marking, or clarifying that border.
  • C. ceasefireLine
    Indicates a demarcation line between opposing parties where active hostilities are formally suspended under a ceasefire agreement.
  • D. involvesFortificationLine
    Indicates a relationship where an event, action, or situation includes or makes use of a specific fortification line as a significant element.
  • E. borderRegime
    Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
  • 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_69f76ebde49481908566cd96b37ccc84 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a000a1d8fa88190a1d82ac746565c48 completed May 10, 2026, 4:31 a.m.
PD Predicate disambiguation batch_6a0008b26eb88190ae03b2309a614774 completed May 10, 2026, 4:25 a.m.
Created at: May 3, 2026, 4:16 p.m.