Triple
T24727666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambala Cantonment Assembly constituency |
E618197
|
entity |
| Predicate | languageUsedInElectionMaterial |
P131808
|
FINISHED |
| Object | English |
—
|
LITERAL 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: English | Statement: [Ambala Cantonment Assembly constituency, languageUsedInElectionMaterial, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInElectionMaterial Context triple: [Ambala Cantonment Assembly constituency, languageUsedInElectionMaterial, English]
-
A.
languageOfCampaigning
Indicates the language used to conduct or communicate a campaign (e.g., political, marketing, or advocacy efforts).
-
B.
languageOfBallots
Indicates the language or languages in which ballots are written or presented.
-
C.
languageOfPoliticalWork
Indicates the language in which a political work (such as a document, speech, or publication) is expressed or written.
-
D.
languageOfPoliticalContext
Indicates the language in which a given political context, discourse, or situation is expressed or conducted.
-
E.
officialLanguageOfProgramMaterials
chosen
Indicates the language officially used in the materials or documentation of a program.
- F. None of above.
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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4 a.m.