Triple
T25284135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau of Indian Standards |
E633891
|
entity |
| Predicate | issuesMark |
P158802
|
FINISHED |
| Object | Hallmark for silver jewellery |
—
|
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: Hallmark for silver jewellery | Statement: [Bureau of Indian Standards, issuesMark, Hallmark for silver jewellery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesMark Context triple: [Bureau of Indian Standards, issuesMark, Hallmark for silver jewellery]
-
A.
issuesMark
chosen
Indicates that one entity assigns or gives a mark, grade, or score to another entity.
-
B.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
C.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
D.
issuesTitle
Indicates that an entity formally grants or assigns an official title or designation to another entity.
-
E.
issueFramedAs
Indicates that one party presents or characterizes an issue in a particular way or perspective to another party or audience.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:19 p.m.