Triple
T24662775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sanjak-bey of Manisa |
E610581
|
entity |
| Predicate | officeHolderTitleInOttomanTurkish |
P93125
|
FINISHED |
| Object | sancak beyi |
—
|
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: sancak beyi | Statement: [sanjak-bey of Manisa, officeHolderTitleInOttomanTurkish, sancak beyi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderTitleInOttomanTurkish Context triple: [sanjak-bey of Manisa, officeHolderTitleInOttomanTurkish, sancak beyi]
-
A.
officeHolderTitleInTurkish
chosen
Indicates the official title or designation of an office holder expressed in the Turkish language.
-
B.
caliphalTitle
Indicates that an entity holds or is designated by a title associated with a caliph or the caliphate.
-
C.
predecessorAsKapudanPasha
Indicates that one entity previously held the office of Kapudan Pasha (Grand Admiral of the Ottoman Navy) immediately before the other entity.
-
D.
officeHolderTitleInArabic
Indicates the official title or designation of an office holder expressed in the Arabic language.
-
E.
officeHolderTitleInLatin
Indicates that the specified office holder’s title is expressed in its Latin-language form.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.