Triple
T25961237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Archaeology, Government of Tamil Nadu |
E645541
|
entity |
| Predicate | typeOfMonumentManaged |
P25584
|
FINISHED |
| Object | temple monuments |
—
|
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: temple monuments | Statement: [Department of Archaeology, Government of Tamil Nadu, typeOfMonumentManaged, temple monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonumentManaged Context triple: [Department of Archaeology, Government of Tamil Nadu, typeOfMonumentManaged, temple monuments]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
C.
isPublicMonument
Indicates that something is officially designated, accessible, and recognized as a monument in a public space.
-
D.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
-
E.
monumentGroup
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 22, 2026, 8:47 a.m.