Triple
T24958532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan an-Nasir Muhammad |
E624540
|
entity |
| Predicate | mamlukRegime |
P157274
|
FINISHED |
| Object | Bahri Mamluks |
—
|
NE NERFINISHED |
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: Bahri Mamluks | Statement: [Sultan an-Nasir Muhammad, mamlukRegime, Bahri Mamluks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mamlukRegime Context triple: [Sultan an-Nasir Muhammad, mamlukRegime, Bahri Mamluks]
-
A.
aimOfMamluks
Indicates that the specified goal, objective, or purpose is attributed to or pursued by the Mamluks.
-
B.
OttomanDynasty
Indicates a dynastic or ruling-family relationship associated with the Ottoman Empire.
-
C.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
D.
underOttomanRuleFrom
Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
-
E.
caliphate
Indicates a relationship in which an authority or governance structure is organized under a caliph, claiming religious and political leadership over a Muslim community or territory.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242b03a081909c676b1884191f17 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:58 a.m.