Triple
T19184712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adikesava Perumal Temple, Sriperumbudur |
E469670
|
entity |
| Predicate | deityGender |
P118405
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [Adikesava Perumal Temple, Sriperumbudur, deityGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityGender Context triple: [Adikesava Perumal Temple, Sriperumbudur, deityGender, male]
-
A.
genderOfReferencedDeity
chosen
Indicates that the relationship specifies the gender associated with a particular referenced deity.
-
B.
includesMaleDeity
Indicates that the referenced set, group, or context contains at least one male deity as a member or participant.
-
C.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
D.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
E.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61f1d9c8190b67555383d821958 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.