Triple
T11102571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapoor |
E262548
|
entity |
| Predicate | script |
P505
|
FINISHED |
| Object | Gurmukhi |
E12238
|
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: Gurmukhi | Statement: [Kapoor, script, Gurmukhi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gurmukhi Context triple: [Kapoor, script, Gurmukhi]
-
A.
Gurmukhi
chosen
Gurmukhi is an Indic writing system primarily used for the Punjabi language and for recording Sikh religious scriptures.
-
B.
Gujarati script
The Gujarati script is an abugida used primarily to write the Gujarati language and related Indo-Aryan languages, derived from the Devanagari script and characterized by the absence of the horizontal headline.
-
C.
Shahmukhi script
Shahmukhi script is a Perso-Arabic–based writing system primarily used for writing the Punjabi language in Pakistan.
-
D.
Sant Bhasha
Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
-
E.
Dogri
Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2c30a481908c45020c37caebe4 |
completed | April 9, 2026, 12:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e7f9b46881909761ed448fa5ce6e |
completed | April 18, 2026, 8:22 p.m. |
Created at: April 8, 2026, 9:27 p.m.