Triple
T4508041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15th Light Dragoons |
E101980
|
entity |
| Predicate | cavalryClass |
P56207
|
FINISHED |
| Object | light cavalry |
—
|
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: light cavalry | Statement: [15th Light Dragoons, cavalryClass, light cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cavalryClass Context triple: [15th Light Dragoons, cavalryClass, light cavalry]
-
A.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
B.
hasCavalrySetting
Indicates that an entity is associated with a context, configuration, or environment specifically involving cavalry.
-
C.
strengthBritishCavalry
Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
-
D.
regimentalCategory
chosen
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
E.
soldierCaste
Indicates that an entity belongs to, or is characterized as part of, a soldier or warrior class within a social or organizational hierarchy.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570f9b1c8190b52ace855dbf6641 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.