Triple
T29139833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Howard "Bunny" Colvin |
E738593
|
entity |
| Predicate | commandedDistrict |
P32961
|
FINISHED |
| Object | Western District |
—
|
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: Western District | Statement: [Major Howard "Bunny" Colvin, commandedDistrict, Western District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedDistrict Context triple: [Major Howard "Bunny" Colvin, commandedDistrict, Western District]
-
A.
militaryDistrict
Indicates that an entity functions as, or is located within, an administrative military district or region under military jurisdiction.
-
B.
commandedRegion
chosen
Indicates that one entity had authoritative control or command over a specific geographic region.
-
C.
commandedForcesFrom
Indicates that one entity held command authority over military or organizational forces originating from another entity.
-
D.
parentUnitMilitaryDistrict
Indicates that one military unit is organizationally subordinate to and contained within a higher-level military district.
-
E.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 11:36 a.m.