Triple
T23194247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gursharan Kaur |
E579831
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kaur |
E438962
|
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: Kaur | Statement: [Gursharan Kaur, familyName, Kaur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaur Context triple: [Gursharan Kaur, familyName, Kaur]
-
A.
Kaur
Kaur is a riverside town in central Gambia situated along the Gambia River and known as a local trading and transport hub.
-
B.
Kaur
Kaur is a historical region in southwestern Sumatra, Indonesia, traditionally associated with the Rejang people and their script.
-
C.
Kaur
chosen
Kaur is a common Sikh and Punjabi surname traditionally used by women, symbolizing equality and courage.
-
D.
Kauravi
Kauravi is a dialect of Hindi-Urdu historically spoken in the Delhi and western Uttar Pradesh region, considered a major basis for the standard Hindi register.
-
E.
Raj Kaur
Raj Kaur was the mother of Maharaja Ranjit Singh, the founder of the Sikh Empire in the early 19th century.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fda64cc8190aeb5ccd8d8d20858 |
completed | April 29, 2026, 4:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c30bcb5d4819088b89ef3aa187791 |
completed | May 19, 2026, 9:43 a.m. |
Created at: April 17, 2026, 4:06 p.m.