Triple
T20133468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conjeevaram |
E490958
|
entity |
| Predicate | isFamousTempleCity |
P48433
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Conjeevaram, isFamousTempleCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamousTempleCity Context triple: [Conjeevaram, isFamousTempleCity, true]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
C.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
D.
hasTempleDistrict
Indicates that a place or settlement contains or is associated with a designated temple district area.
-
E.
hasNotableTemple
chosen
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66763ee908190af64af31b4ca2377 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.