Triple
T25257314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Paper Mill, Hoshangabad |
E633204
|
entity |
| Predicate | typeOfPaperProduced |
P172316
|
FINISHED |
| Object | watermarked security paper |
—
|
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: watermarked security paper | Statement: [Security Paper Mill, Hoshangabad, typeOfPaperProduced, watermarked security paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPaperProduced Context triple: [Security Paper Mill, Hoshangabad, typeOfPaperProduced, watermarked security paper]
-
A.
usesPaperType
Indicates that one entity employs or operates with a specific type or category of paper.
-
B.
paper1Type
Indicates that one entity is classified as the primary or first type/category of the associated paper entity.
-
C.
mainsPaperType
Indicates the type or category of paper associated with a mains (main) examination or assessment.
-
D.
hasPaper
Indicates that an entity possesses, is associated with, or includes a specific paper (such as a document, publication, or written work) in some relevant context.
-
E.
paperQuality
Indicates the level or characteristics of quality associated with a paper or written work.
- F. None of above. chosen
Provenance (4 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 21, 2026, 1:13 p.m.