Triple
T28744307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagiroad |
E731324
|
entity |
| Predicate | paperMillOwner |
P85508
|
FINISHED |
| Object | Hindustan Paper Corporation Limited |
—
|
NE NERFINISHED |
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: Hindustan Paper Corporation Limited | Statement: [Jagiroad, paperMillOwner, Hindustan Paper Corporation Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paperMillOwner Context triple: [Jagiroad, paperMillOwner, Hindustan Paper Corporation Limited]
-
A.
paperMillOriginalOperator
Indicates that an entity was the original operator (first operating organization or company) of a given paper mill.
-
B.
hasPaperMill
chosen
Indicates that one entity possesses, contains, or is the location of a paper mill.
-
C.
paperMillLaterOperator
Indicates that an entity served as an operator of a paper mill at a later time or subsequent period relative to another operator or timeframe.
-
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.
printingAuthority
Indicates the entity responsible for producing or issuing a physical or printed version of another entity.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:04 a.m.