Triple
T17792934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Malik al-Zahir Baibars |
E444212
|
entity |
| Predicate | militaryRankBeforeSultan |
P128938
|
FINISHED |
| Object | Mamluk emir |
—
|
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: Mamluk emir | Statement: [al-Malik al-Zahir Baibars, militaryRankBeforeSultan, Mamluk emir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankBeforeSultan Context triple: [al-Malik al-Zahir Baibars, militaryRankBeforeSultan, Mamluk emir]
-
A.
predecessorAsKapudanPasha
Indicates that one entity previously held the office of Kapudan Pasha (Grand Admiral of the Ottoman Navy) immediately before the other entity.
-
B.
successorAsKapudanPasha
Indicates that one entity succeeded another in the role or office of Kapudan Pasha (Grand Admiral of the Ottoman Navy).
-
C.
predecessorAsValideSultan
Indicates that one entity served as the immediately preceding legitimate sultan to another entity.
-
D.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
E.
predecessorAsSultan
Indicates that one entity previously held the position of sultan before another entity, directly preceding them in that role.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879859408190875835bd255e1185 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.