Triple
T32042394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Registration Department |
E818249
|
entity |
| Predicate | sectoralCategory |
P71
|
FINISHED |
| Object | revenue and registration |
—
|
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: revenue and registration | Statement: [Tamil Nadu Registration Department, sectoralCategory, revenue and registration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectoralCategory Context triple: [Tamil Nadu Registration Department, sectoralCategory, revenue and registration]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
-
C.
sectorOfOperation
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
D.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
E.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4bf5d808190a47113f83dc522fb |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:19 a.m.