Triple
T25961647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appu lingam |
E645553
|
entity |
| Predicate | isEnshrinedIn |
P59560
|
FINISHED |
| Object | Jambukeswarar Temple |
—
|
NE NERFINISHED |
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: Jambukeswarar Temple | Statement: [Appu lingam, isEnshrinedIn, Jambukeswarar Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnshrinedIn Context triple: [Appu lingam, isEnshrinedIn, Jambukeswarar Temple]
-
A.
enshrinedSince
Indicates that something has been formally established, preserved, or honored starting from a specific point in time.
-
B.
enshrinedWithin
chosen
Indicates that one entity is formally preserved, honored, or safeguarded inside or as part of another entity, often with a sense of protection or reverence.
-
C.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
hasCommemorativeStructure
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c70f208190a8154d17108e47d9 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:47 a.m.