Triple

T33898291
Position Surface form Disambiguated ID Type / Status
Subject Loudoun County, Colony of Virginia E868974 entity
Predicate hadMilitia P177884 FINISHED
Object Loudoun County colonial militia 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: Loudoun County colonial militia | Statement: [Loudoun County, Colony of Virginia, hadMilitia, Loudoun County colonial militia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadMilitia
Context triple: [Loudoun County, Colony of Virginia, hadMilitia, Loudoun County colonial militia]
  • A. hadMilitaryObligationsTo
    Indicates that one party was bound by duty or law to provide military service, support, or protection to another party.
  • B. hadMilitaryPost
    Indicates that an entity held an official position or assignment within a military organization.
  • C. musteredIntoService
    Indicates that an entity has been formally enrolled or assembled into active duty or official service under an authority.
  • D. musteredIn
    Indicates that an individual or unit was formally enrolled, assembled, or brought into active service within an organization, typically a military force.
  • E. hadMilitaryFollowing
    Indicates that an entity was supported or backed by a group of military personnel or forces.
  • F. None of above. chosen

Provenance (4 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_69f34997703c8190866b1d404bce531f completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
PDg Predicate description generation batch_69f70519f114819080659840c04d7911 completed May 3, 2026, 8:19 a.m.
Created at: May 1, 2026, 1:48 a.m.