Triple
T32118027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sivaganga district |
E820289
|
entity |
| Predicate | hasHeritageTownType |
P5929
|
FINISHED |
| Object | Chettinad trading towns |
—
|
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: Chettinad trading towns | Statement: [Sivaganga district, hasHeritageTownType, Chettinad trading towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageTownType Context triple: [Sivaganga district, hasHeritageTownType, Chettinad trading towns]
-
A.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
B.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
C.
hasHeritageStatusWithin
Indicates that something holds a recognized heritage designation or status within a specified area, jurisdiction, or context.
-
D.
heritageType
chosen
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 12:28 a.m.