Triple
T3211830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parthasarathy Temple, Triplicane |
E67297
|
entity |
| Predicate | gopuram |
P18959
|
FINISHED |
| Object | eastern gopuram |
—
|
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: eastern gopuram | Statement: [Parthasarathy Temple, Triplicane, gopuram, eastern gopuram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gopuram Context triple: [Parthasarathy Temple, Triplicane, gopuram, eastern gopuram]
-
A.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
B.
templeType
chosen
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
D.
typicalShrineFeature
Indicates that something is a characteristic or commonly found element of a shrine.
-
E.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaaba224c8190ad2f4e0ed1c2ca4a |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.