Triple

T2030572
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vimy Ridge E44505 entity
Predicate defensiveWorks P8412 FINISHED
Object German trenches and concrete machine-gun nests 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: German trenches and concrete machine-gun nests | Statement: [Battle of Vimy Ridge, defensiveWorks, German trenches and concrete machine-gun nests]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defensiveWorks
Context triple: [Battle of Vimy Ridge, defensiveWorks, German trenches and concrete machine-gun nests]
  • A. defensiveStructure chosen
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • B. defensiveOperation
    Indicates actions or measures undertaken to protect, guard, or defend a target against threats or attacks.
  • C. defends
    Indicates that one entity protects or supports another entity against attack, criticism, or harm.
  • D. defensiveTask
    Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
  • E. defender
    Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
  • 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_69a889144f2481909932f0746a93023d completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb915c9548190809d08c4d67466fb completed March 7, 2026, 5:35 a.m.
PD Predicate disambiguation batch_69abb7a656248190ac2ced196b35bc6b completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:38 p.m.