Triple
T115236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punjab |
E2323
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Punjabi language |
E3585
|
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: Punjabi language | Statement: [Punjab, knownFor, Punjabi language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Punjabi language Context triple: [Punjab, knownFor, Punjabi language]
-
A.
Punjabi language
chosen
Punjabi language is an Indo-Aryan language widely spoken in the Punjab region of India and Pakistan and among large diaspora communities worldwide.
-
B.
Sindhi
Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
-
C.
Urdu language
Urdu is a major South Asian language, written in a Perso-Arabic script and widely used in Pakistan and parts of India in literature, media, and everyday communication.
-
D.
Gurmukhi
Gurmukhi is an Indic writing system primarily used for the Punjabi language and for recording Sikh religious scriptures.
-
E.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a256f1278881909dc9c17113d2cca2 |
completed | Feb. 28, 2026, 2:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a29e47972c819084658ada85db97d3 |
completed | Feb. 28, 2026, 7:50 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.