Triple
T5049484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanchipuram |
E113747
|
entity |
| Predicate | notableStructureType |
P25584
|
FINISHED |
| Object | Dravidian-style gopurams |
—
|
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: Dravidian-style gopurams | Statement: [Kanchipuram, notableStructureType, Dravidian-style gopurams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStructureType Context triple: [Kanchipuram, notableStructureType, Dravidian-style gopurams]
-
A.
monumentType
chosen
Indicates the specific kind or category of monument that an entity is classified as.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
buildingNamed
Indicates that a particular building is known or referred to by a specified name.
-
D.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
E.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.