Triple
T23413794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circassian Mamluk dynasty |
E560148
|
entity |
| Predicate | rulingClassOrigin |
P78018
|
FINISHED |
| Object | military slaves |
—
|
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: military slaves | Statement: [Circassian Mamluk dynasty, rulingClassOrigin, military slaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingClassOrigin Context triple: [Circassian Mamluk dynasty, rulingClassOrigin, military slaves]
-
A.
rulingClassBackground
chosen
Indicates that an entity comes from, or is associated with, a socially or politically dominant (ruling) class background.
-
B.
hadRulingClass
Indicates that a particular group or class held dominant political, economic, or social power over a society or entity.
-
C.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
D.
ethnicGroupOfRulers
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
E.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a513502881909f33a43bfd5e63a7 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.