Triple
T17154721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalifa bin Salman Al Khalifa |
E416313
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Khalifa |
E236945
|
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: Khalifa | Statement: [Khalifa bin Salman Al Khalifa, givenName, Khalifa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khalifa Context triple: [Khalifa bin Salman Al Khalifa, givenName, Khalifa]
-
A.
Khalifa
chosen
Khalifa is a masculine Arabic given name commonly used across the Middle East and North Africa, meaning "successor" or "steward."
-
B.
Khalaf
Khalaf is an Arabic surname commonly borne by individuals and families across the Middle East and the broader Arab diaspora.
-
C.
Walid
Walid is a masculine given name of Arabic origin commonly used across the Middle East and North Africa.
-
D.
Tamīm
Tamīm is an Arabic given name and surname, commonly used across the Arab and Muslim world and borne by several notable historical and contemporary figures.
-
E.
Nayef
Nayef is a masculine given name of Arabic origin commonly used in the Arab world.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40a6b7c8190838e588c4fd81d95 |
completed | April 18, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01415f3cd481908e96ca294cf3b247 |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:37 a.m.