Triple
T38462569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Asian empires |
E912488
|
entity |
| Predicate | usedMilitaryCavalry |
P190769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Central Asian empires, usedMilitaryCavalry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMilitaryCavalry Context triple: [Central Asian empires, usedMilitaryCavalry, true]
-
A.
hasCavalryHeritage
Indicates that an entity has a historical or traditional connection to cavalry forces or mounted military service.
-
B.
strengthBritishCavalry
Indicates the numerical or qualitative level of military power or effectiveness possessed by British cavalry forces.
-
C.
hasCavalryRole
Indicates that an entity serves in, is assigned to, or performs duties associated with a cavalry role.
-
D.
usedChariots
Indicates that one entity employed or utilized chariots in relation to another entity, event, or context.
-
E.
hasCavalrySetting
Indicates that an entity is associated with a context, configuration, or environment specifically involving cavalry.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcce7a25848190bdc66efcbc7cae3a |
completed | May 7, 2026, 5:40 p.m. |
Created at: May 3, 2026, 4:31 p.m.