Triple
T3567208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamluk dynasty of Delhi |
E75477
|
entity |
| Predicate | militaryBasis |
P50410
|
FINISHED |
| Object | Turkic slave 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: Turkic slave cavalry | Statement: [Mamluk dynasty of Delhi, militaryBasis, Turkic slave cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBasis Context triple: [Mamluk dynasty of Delhi, militaryBasis, Turkic slave cavalry]
-
A.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
B.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
C.
militaryInstallationType
Indicates the specific category or kind of military installation associated with an entity (e.g., base, fort, airfield, naval station).
-
D.
fleetBase
Indicates that one entity serves as the primary homeport, headquarters, or main operating base for a fleet associated with the other entity.
-
E.
hasMilitaryPresence
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ab51d881908f004fae47ab09d9 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:21 p.m.