Triple
T24471254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Battalion, 5th Cavalry Regiment |
E617105
|
entity |
| Predicate | higherRegimentalUnit |
P156229
|
FINISHED |
| Object | 5th Cavalry Regiment |
—
|
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: 5th Cavalry Regiment | Statement: [1st Battalion, 5th Cavalry Regiment, higherRegimentalUnit, 5th Cavalry Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherRegimentalUnit Context triple: [1st Battalion, 5th Cavalry Regiment, higherRegimentalUnit, 5th Cavalry Regiment]
-
A.
raisedRegiment
Indicates that an entity organized, formed, or brought into existence a specific military regiment.
-
B.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
C.
guardRegiment
Indicates that one entity serves as a protective or security regiment for another entity.
-
D.
notableMilitaryUnit
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some context.
-
E.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29943e9cc81909f1742c778bf3587 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.