Triple
T38007620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeological authorities of Maharashtra |
E948275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-level heritage authority |
C44846
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: state-level heritage authority Context triple: [Archaeological authorities of Maharashtra, instanceOf, state-level heritage authority]
-
A.
regional heritage authority
A regional heritage authority is an organization responsible for identifying, protecting, managing, and promoting cultural and historical assets within a specific geographic region.
-
B.
provincial heritage authority
chosen
A provincial heritage authority is a government body responsible for identifying, protecting, managing, and promoting cultural and historical resources within a specific province or regional jurisdiction.
-
C.
State Heritage Area
A State Heritage Area is a geographically defined place recognized and protected by a state government for its outstanding cultural, historical, or natural significance.
-
D.
National Heritage Area
A National Heritage Area is a region designated by the U.S. Congress where natural, cultural, and historic resources form a cohesive, nationally important landscape managed through partnerships rather than federal land ownership.
-
E.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
- F. None of above.
Provenance (1 batch)
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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.