Triple
T365859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian American |
E7957
|
entity |
| Predicate | languageUsed |
P238
|
FINISHED |
| Object | Punjabi |
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 | Statement: [Asian American, languageUsed, Punjabi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Punjabi Context triple: [Asian American, languageUsed, Punjabi]
-
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.
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.
-
D.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
-
E.
Khari Boli
Khari Boli is a major dialect of the Hindi-Urdu language continuum, historically associated with the Delhi region and serving as the primary basis for Standard Hindi.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe7d4d0819083daeb7686ae1914 |
completed | Feb. 28, 2026, 1:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3eca938988190b4490e086f25474e |
completed | March 1, 2026, 7:37 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.