Triple
T20256453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Isaac Trimble |
E498713
|
entity |
| Predicate | engagementTypeAtGettysburg |
P3663
|
FINISHED |
| Object | frontal assault |
—
|
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: frontal assault | Statement: [Division of Isaac Trimble, engagementTypeAtGettysburg, frontal assault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementTypeAtGettysburg Context triple: [Division of Isaac Trimble, engagementTypeAtGettysburg, frontal assault]
-
A.
engagementType
chosen
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
B.
higherCommanderAtGettysburg
Indicates that one entity served as the superior military commander of another entity during the Battle of Gettysburg.
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
roleAtGettysburg
Indicates the specific role, position, or function an entity held in relation to the Battle of Gettysburg.
-
E.
dayOfKeyGettysburgAction
Indicates the specific calendar day on which a key action or event related to the Battle of Gettysburg occurred.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c6693081908ff8bec12f212f7b |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.