Triple
T13112538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan bin Abdulaziz Al Saud |
E311007
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sultan |
E869365
|
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: Sultan | Statement: [Sultan bin Abdulaziz Al Saud, givenName, Sultan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sultan Context triple: [Sultan bin Abdulaziz Al Saud, givenName, Sultan]
-
A.
Sultan
The Sultan was the supreme monarch of the Ottoman Empire, wielding ultimate political, military, and religious authority over its vast territories.
-
B.
Sultan
Sultan is a writer known for creating works under the pseudonym "2U."
-
C.
Sultan
chosen
Sultan is a surname of Arabic origin historically associated with rulership and authority in various Muslim societies.
-
D.
Sulṭán
Sulṭán is the fourth month of the Baháʼí Badíʻ calendar, whose name signifies "sovereignty" or "dominion."
-
E.
The Sultan
The Sultan is the benevolent yet somewhat naive ruler of Agrabah and Princess Jasmine’s father in Disney’s Aladdin story.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e27f5c4481909bc323c9d0c83dc9 |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 9:05 p.m.