Triple
T3810536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Stony Point |
E93121
|
entity |
| Predicate | orderOfBattleFeature |
P51977
|
FINISHED |
| Object | columns of attack |
—
|
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: columns of attack | Statement: [Battle of Stony Point, orderOfBattleFeature, columns of attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderOfBattleFeature Context triple: [Battle of Stony Point, orderOfBattleFeature, columns of attack]
-
A.
commandedForcesOf
Indicates that one entity held command authority over the military or armed forces associated with another entity.
-
B.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
C.
numberOfBattalions
Indicates the quantitative relationship specifying how many battalions are associated with a given entity or context.
-
D.
militaryFormationOf
Indicates that one entity is a military unit or formation that is organizationally part of, or derived from, another entity.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:16 p.m.