Triple
T5060747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehmed III |
E114015
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Mehmed |
E515608
|
NE 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: Mehmed | Statement: [Mehmed III, givenName, Mehmed]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mehmed Context triple: [Mehmed III, givenName, Mehmed]
-
A.
Mehmed
chosen
Mehmed was the given name of Mehmed V, the Ottoman sultan who ruled during the early 20th century and World War I.
-
B.
Mehmed Selim
Mehmed Selim was an Ottoman prince, the son of Sultan Abdul Hamid II, who lived during the late period of the Ottoman Empire.
-
C.
Mehmed II
Mehmed II, also known as Mehmed the Conqueror, was the Ottoman sultan who captured Constantinople in 1453 and transformed the empire into a major regional power.
-
D.
Mehmed I
Mehmed I was an early 15th-century Ottoman sultan who reunified the fractured empire after a civil war and helped restore its stability and expansion.
-
E.
Mahomet I
Mahomet I was a notable leader of the Mohegan tribe, recognized for his role in guiding and representing his people.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfd2366a3c819097391ad8731c21a8 |
completed | March 22, 2026, 11:27 a.m. |
Created at: March 20, 2026, 1:38 p.m.