Triple

T25520653
Position Surface form Disambiguated ID Type / Status
Subject Massachusetts 1st Heavy Artillery Regiment E639636 entity
Predicate garrisonDutyLocation P70155 FINISHED
Object defenses of Washington, D.C. 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: defenses of Washington, D.C. | Statement: [Massachusetts 1st Heavy Artillery Regiment, garrisonDutyLocation, defenses of Washington, D.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: garrisonDutyLocation
Context triple: [Massachusetts 1st Heavy Artillery Regiment, garrisonDutyLocation, defenses of Washington, D.C.]
  • A. garrisonDuty
    Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
  • B. garrisonOrMobilizationPoint chosen
    Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
  • C. garrisonOrRecruitmentArea
    Indicates an area designated for stationing military forces or for recruiting personnel into those forces.
  • D. garrisonOrHQ
    Indicates that an entity serves as a military garrison or headquarters location for another entity.
  • E. garrisonRegion
    Indicates that a military force is stationed in and responsible for defending a specific region.
  • 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_69e75dbe32e48190a62d749a0ff2a96a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f836387c8190813f5c202ff47a8c completed May 2, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69f468421ba08190880eac99135e5970 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 3 p.m.