Triple
T20572527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haseki Sultan |
E505137
|
entity |
| Predicate | courtRankRelativeToOtherWomen |
P62203
|
FINISHED |
| Object | above kadin |
—
|
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: above kadin | Statement: [Haseki Sultan, courtRankRelativeToOtherWomen, above kadin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtRankRelativeToOtherWomen Context triple: [Haseki Sultan, courtRankRelativeToOtherWomen, above kadin]
-
A.
courtRank
chosen
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
-
B.
hasPatriarchalEquivalentRank
Indicates that one entity holds a rank that is equivalent, in a patriarchal hierarchy or system, to the rank held by another entity.
-
C.
defendantRank
Indicates the hierarchical position or status assigned to a defendant relative to other defendants in a legal case.
-
D.
marriedToRank
Indicates that one entity is married to another entity who holds a specific rank or position.
-
E.
isRankedAlongside
Indicates that two or more entities share the same or very similar rank, status, or position within a given ordering or hierarchy.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a906f0508190ac698233738f4452 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.