Triple
T9194073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udbodhan House, Calcutta |
E220659
|
entity |
| Predicate | languageOfAssociatedPublication |
P17914
|
FINISHED |
| Object | Bengali |
—
|
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: Bengali | Statement: [Udbodhan House, Calcutta, languageOfAssociatedPublication, Bengali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAssociatedPublication Context triple: [Udbodhan House, Calcutta, languageOfAssociatedPublication, Bengali]
-
A.
publicationLanguageOfSourceWork
Indicates the language in which the original source work was published.
-
B.
languageOfParentWork
Indicates that the specified language is the language in which the parent (original or containing) work is expressed.
-
C.
originalPublicationLanguageVariant
Indicates that one language is a specific variant or version of the language in which a work was originally published.
-
D.
languageOfWritings
chosen
Indicates that a specified language is the one in which certain writings or written works are composed.
-
E.
languageOfUnderlyingWork
Indicates the language in which the original or underlying work (from which a derived or related work stems) is expressed.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c3614c81909e26417e00fdfa11 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.