Triple
T3077782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry W. Halleck |
E64177
|
entity |
| Predicate | roleInMexicanAmericanWar |
P45733
|
FINISHED |
| Object | Army engineer |
—
|
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: Army engineer | Statement: [Henry W. Halleck, roleInMexicanAmericanWar, Army engineer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMexicanAmericanWar Context triple: [Henry W. Halleck, roleInMexicanAmericanWar, Army engineer]
-
A.
roleInSpanishCivilWar
Indicates the specific involvement or function an entity had in the context of the Spanish Civil War.
-
B.
opponentInAmericanCivilWar
Indicates that two entities were on opposing sides in the American Civil War.
-
C.
roleInAmericanRevolution
Indicates that an entity had a specific role, position, or involvement in events or activities related to the American Revolution.
-
D.
unionArmy
Indicates that an entity served in, was part of, or is otherwise affiliated with the Union Army (the United States Army of the North) during the American Civil War.
-
E.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a6f6148190ae5cd6e45eda9006 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:02 p.m.