Triple
T32579994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean Khanate |
E832754
|
entity |
| Predicate | hasMemberOfRulingElite |
P68121
|
FINISHED |
| Object | Mubarak Giray |
—
|
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: Mubarak Giray | Statement: [Crimean Khanate, hasMemberOfRulingElite, Mubarak Giray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberOfRulingElite Context triple: [Crimean Khanate, hasMemberOfRulingElite, Mubarak Giray]
-
A.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
B.
hasRoyalFamilyMember
chosen
Indicates that one entity is a member of the royal family associated with another entity.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
hasPrestigiousRace
Indicates that an entity is associated with a race or competition that is considered highly prestigious or of elite status.
-
E.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 1:04 a.m.