Triple
T22462610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stag |
E555266
|
entity |
| Predicate | regulatoryCategoryInIndia |
P72103
|
FINISHED |
| Object | IMFL whisky |
—
|
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: IMFL whisky | Statement: [Royal Stag, regulatoryCategoryInIndia, IMFL whisky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryCategoryInIndia Context triple: [Royal Stag, regulatoryCategoryInIndia, IMFL whisky]
-
A.
legalCategoryInIndia
chosen
Indicates that an entity belongs to a specific legally defined category or classification under Indian law.
-
B.
legalStatusAccordingToIndia
Indicates the legal status or classification of an entity as defined specifically by the laws and regulations of India.
-
C.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
D.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
E.
regulationStatus
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b80983081908084947b2e31c9d4 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.