Triple
T25444765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots Greys |
E637601
|
entity |
| Predicate | typeOfCavalry |
P6154
|
FINISHED |
| Object | heavy 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: heavy cavalry | Statement: [Scots Greys, typeOfCavalry, heavy cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCavalry Context triple: [Scots Greys, typeOfCavalry, heavy cavalry]
-
A.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
B.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
C.
hasCavalrySetting
Indicates that an entity is associated with a context, configuration, or environment specifically involving cavalry.
-
D.
strengthBritishCavalry
Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
-
E.
RashidunCavalryComponent
Indicates that something serves as a cavalry component or unit within the Rashidun military forces.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 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 21, 2026, 2 p.m.