Triple

T34828244
Position Surface form Disambiguated ID Type / Status
Subject 5th Massachusetts Cavalry Regiment E1003991 entity
Predicate hasSoldierDemographic P165997 FINISHED
Object formerly enslaved men 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: formerly enslaved men | Statement: [5th Massachusetts Cavalry Regiment, hasSoldierDemographic, formerly enslaved men]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSoldierDemographic
Context triple: [5th Massachusetts Cavalry Regiment, hasSoldierDemographic, formerly enslaved men]
  • A. hasSoldier
    Indicates that one entity possesses, employs, or is associated with a soldier or group of soldiers.
  • B. hasMilitaryStatus
    Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
  • C. hasMilitaryClass
    Indicates that an entity belongs to, is assigned to, or is categorized under a specific military class or classification.
  • D. regimentalEthnicity chosen
    Indicates that a military regiment is associated with a particular ethnic group, typically in terms of its composition or identity.
  • E. hasMilitaryType
    Indicates that an entity is associated with or classified under a specific military category, role, or type.
  • 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_69f76db7d1b4819093bd4912d80d845d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd57ba740c8190bd1d40166fccccb7 completed May 8, 2026, 3:25 a.m.
PD Predicate disambiguation batch_69fd55ee82b881908a639da3a41b3af6 completed May 8, 2026, 3:18 a.m.
Created at: May 3, 2026, 4 p.m.