Triple
T21916678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jnanpith |
E541197
|
entity |
| Predicate | hasPublicationProgram |
P75827
|
FINISHED |
| Object | multi-language literary publishing |
—
|
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: multi-language literary publishing | Statement: [Jnanpith, hasPublicationProgram, multi-language literary publishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicationProgram Context triple: [Jnanpith, hasPublicationProgram, multi-language literary publishing]
-
A.
hasPublishingProgram
chosen
Indicates that an entity operates or maintains a formal program or initiative for publishing content, works, or materials.
-
B.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
C.
hasPublicProgram
Indicates that an entity offers or participates in a program or initiative that is accessible to the general public.
-
D.
hasPublicationMedium
Indicates the medium or channel through which a work or publication is disseminated or made available.
-
E.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233858308190a877d8015db4d380 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:43 p.m.