Triple

T22111958
Position Surface form Disambiguated ID Type / Status
Subject Charlottenlund E546438 entity
Predicate fortificationPurpose P119202 FINISHED
Object coastal defense of Copenhagen 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: coastal defense of Copenhagen | Statement: [Charlottenlund, fortificationPurpose, coastal defense of Copenhagen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fortificationPurpose
Context triple: [Charlottenlund, fortificationPurpose, coastal defense of Copenhagen]
  • A. fortifiedWith
    Indicates that something has been strengthened, enhanced, or reinforced by the addition of a specified substance, feature, or element.
  • B. reasonForFortification chosen
    Indicates the underlying motivation or purpose for which a fortification was constructed, strengthened, or maintained.
  • C. fortifiedIn
    Indicates that one entity has been strengthened, reinforced, or protected within or by another entity (such as a structure, location, or medium).
  • D. fortificationSystem
    Indicates a defensive structure or network designed to protect a place or area from attack.
  • E. fortificationCommanded
    Indicates that one entity holds authority over and directs the defense or operation of a particular fortification or fortified 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12949cc7881908898ca7dc130f57f completed April 28, 2026, 9:40 p.m.
PD Predicate disambiguation batch_69e71b2ed7348190b6fa2e52f54393fb completed April 21, 2026, 6:37 a.m.
Created at: April 16, 2026, 8:31 p.m.