Triple
T32888999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Raghavendra Swamy Temple |
E841279
|
entity |
| Predicate | eraOfSaint |
P179079
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Sri Raghavendra Swamy Temple, eraOfSaint, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfSaint Context triple: [Sri Raghavendra Swamy Temple, eraOfSaint, 17th century]
-
A.
eraOfSignificance
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
B.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
C.
eraDepicted
Indicates that a work or representation portrays, illustrates, or is set in a particular historical era or time period.
-
D.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
E.
eraReference
Indicates a temporal relationship where something is associated with, situated in, or characterized by a particular historical era or time period.
- F. None of above. chosen
Provenance (4 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: May 1, 2026, 1:18 a.m.