Triple
T35314202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Jackson Massacre |
E1019856
|
entity |
| Predicate | commanderOfUnionForces |
P194279
|
FINISHED |
| Object | Nathaniel Lyon |
—
|
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: Nathaniel Lyon | Statement: [Camp Jackson Massacre, commanderOfUnionForces, Nathaniel Lyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderOfUnionForces Context triple: [Camp Jackson Massacre, commanderOfUnionForces, Nathaniel Lyon]
-
A.
commandingUnionArmy
Indicates that one entity holds the role or responsibility of leading and directing the Union Army.
-
B.
commanderAtBattleOfMobileBay
Indicates that the subject served as a commanding officer during the Battle of Mobile Bay.
-
C.
primaryConfederateCommander
Indicates that one entity serves as the main commanding officer of Confederate forces for the other entity in a specific context or engagement.
-
D.
commanderUnitedStates
Indicates that one entity serves as the commander of a United States military or governmental unit, mission, or operation.
-
E.
appointedCommanderOfArmyOfThePotomacOn
Indicates that someone was officially appointed as commander of the Army of the Potomac on a specific date.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: May 3, 2026, 4:03 p.m.