Triple

T23862749
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cheat Mountain E592492 entity
Predicate relatedFortification P22477 FINISHED
Object Fort Milroy (Cheat Summit Fort) 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: Fort Milroy (Cheat Summit Fort) | Statement: [Battle of Cheat Mountain, relatedFortification, Fort Milroy (Cheat Summit Fort)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedFortification
Context triple: [Battle of Cheat Mountain, relatedFortification, Fort Milroy (Cheat Summit Fort)]
  • A. fortifiedSite
    Indicates a site that has been strengthened or defended with protective structures or measures against attack.
  • B. isFortificationGatewayOf
    Indicates that a gateway or entrance structure serves as an access point or defensive portal belonging to a specific fortification.
  • C. wasFortifiedBy
    Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
  • D. fortificationTypeDefended
    Indicates the specific type of fortification that an entity is responsible for defending or protecting.
  • E. hasFortifications chosen
    Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
  • 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_69e25d22eb488190914b193aff952e83 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cae16df4819081a8b3a395e45118 completed April 29, 2026, 9:09 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:13 p.m.