Triple
T9280710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desi Lydic |
E223058
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Desi |
E329597
|
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: Desi | Statement: [Desi Lydic, givenName, Desi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Desi Context triple: [Desi Lydic, givenName, Desi]
-
A.
Desi
chosen
Desi is a given name commonly used as a shortened or affectionate form of the name Desmond.
-
B.
Desiya
Desiya is a regional dialect spoken in parts of Odisha, India, influenced by Odia and neighboring tribal and Indo-Aryan languages.
-
C.
Indi
Indi is an Australian federal electoral division in the state of Victoria, encompassing a largely rural and regional area in the state's northeast.
-
D.
Hindiyah
Hindiyah is a town in Iraq, located in the Babil Governorate, known as the birthplace of former Prime Minister Nouri al-Maliki.
-
E.
Dakhni
Dakhni is a historical Indo-Aryan language variety that developed in the Deccan region of India, blending early Urdu/Hindavi with local languages and Persian-Arabic influences.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cd9a1c8190af0521baa428ce10 |
completed | April 1, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b1fef1508190a9bf1a55dd39c0ac |
completed | April 4, 2026, 6:38 a.m. |
Created at: March 30, 2026, 7:34 p.m.