Triple
T23206523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usman |
E580471
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Othman |
—
|
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: Othman | Statement: [Usman, hasVariant, Othman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Othman Context triple: [Usman, hasVariant, Othman]
-
A.
Osman
chosen
Osman is the principal male character in the traditional Croatian Moreška sword dance, typically portrayed as the leader of the invading "black" army.
-
B.
Osman
Osman is a common Somali surname shared by many individuals, including prominent political and public figures.
-
C.
Ottman
Ottman is a surname most notably associated with John Ottman, an American film editor and composer known for his work on major Hollywood films.
-
D.
Murat
Murat is a historic small town in south-central France, known for its volcanic landscape setting in the Cantal region and its traditional stone architecture.
-
E.
Osmanoğlu
Osmanoğlu is the surname borne by descendants of the Ottoman imperial dynasty, historically associated with the ruling house of the Ottoman Empire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907cd62c8190afee1e963b170727 |
completed | April 29, 2026, 5 a.m. |
Created at: April 17, 2026, 4:07 p.m.