Triple
T6591279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Paoli |
E159362
|
entity |
| Predicate | AmericanCommanderRank |
P30999
|
FINISHED |
| Object | Brigadier General |
—
|
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: Brigadier General | Statement: [Battle of Paoli, AmericanCommanderRank, Brigadier General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AmericanCommanderRank Context triple: [Battle of Paoli, AmericanCommanderRank, Brigadier General]
-
A.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
B.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
airCommanderRank
Indicates that one entity holds the rank or position of air commander relative to another entity (such as a force, unit, or operation).
-
E.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.