Triple
T25393389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Squadron, 3rd Cavalry Regiment |
E636226
|
entity |
| Predicate | roleWithinRegiment |
P9463
|
FINISHED |
| Object | maneuver squadron |
—
|
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: maneuver squadron | Statement: [4th Squadron, 3rd Cavalry Regiment, roleWithinRegiment, maneuver squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinRegiment Context triple: [4th Squadron, 3rd Cavalry Regiment, roleWithinRegiment, maneuver squadron]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
regimentalStatus
Indicates the formal organizational state or condition of a military regiment within a given structure or timeframe.
-
C.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
D.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
E.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f56572b9288190abaf921c761fd843 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:49 p.m.