Triple
T28715157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dade’s Massacre |
E729939
|
entity |
| Predicate | combatant_US_unit |
P19840
|
FINISHED |
| Object | Company B, 2nd U.S. Artillery |
—
|
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: Company B, 2nd U.S. Artillery | Statement: [Dade’s Massacre, combatant_US_unit, Company B, 2nd U.S. Artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatant_US_unit Context triple: [Dade’s Massacre, combatant_US_unit, Company B, 2nd U.S. Artillery]
-
A.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
B.
notableMilitaryUnit
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some context.
-
C.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
D.
USForces
chosen
Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
-
E.
stateMilitaryUnitOf
Indicates that a military unit is organized, controlled, or officially associated with a particular state or governmental jurisdiction.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 5:50 a.m.