Triple

T37535212
Position Surface form Disambiguated ID Type / Status
Subject Secteur fortifié du Rhône E933175 entity
Predicate fortificationStyle P172092 FINISHED
Object Maginot Line design principles 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: Maginot Line design principles | Statement: [Secteur fortifié du Rhône, fortificationStyle, Maginot Line design principles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fortificationStyle
Context triple: [Secteur fortifié du Rhône, fortificationStyle, Maginot Line design principles]
  • A. fortifiedChurchStyle
    Indicates that something is designed, built, or characterized in the architectural manner of a fortified church, combining religious and defensive features.
  • B. involvesFortificationType chosen
    Indicates that the relationship or action includes or is associated with a specific type of fortification (e.g., defensive structure or fortified feature).
  • C. fortificationSystem
    Indicates a defensive structure or network designed to protect a place or area from attack.
  • D. fortifiedIn
    Indicates that one entity has been strengthened, reinforced, or protected within or by another entity (such as a structure, location, or medium).
  • E. fortificationBuilt
    Indicates that a fortification was constructed or established, linking the structure to the event or agent responsible for its building.
  • 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_69f76ec999288190ae26ec7b6aea7046 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba5eec0448190a5e6f0c43fdcd0e3 completed May 6, 2026, 8:34 p.m.
PD Predicate disambiguation batch_69fba34edd548190bfa980e6e16e0a88 completed May 6, 2026, 8:23 p.m.
Created at: May 3, 2026, 4:17 p.m.