Triple
T32042379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu Registration Department |
E818249
|
entity |
| Predicate | documentTypeRegistered |
P176050
|
FINISHED |
| Object | sale deeds |
—
|
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: sale deeds | Statement: [Tamil Nadu Registration Department, documentTypeRegistered, sale deeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentTypeRegistered Context triple: [Tamil Nadu Registration Department, documentTypeRegistered, sale deeds]
-
A.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
B.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
C.
documentTypeContext
Indicates the contextual relationship between a document and its specific type or classification within a given setting or usage scenario.
-
D.
documentTypeApproved
Indicates that a specific type or category of document has been formally reviewed and granted approval for use or processing.
-
E.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 12:19 a.m.