Triple
T22308913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parshvanath Jain Temple |
E551460
|
entity |
| Predicate | isSacredHillTemple |
P140525
|
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: [Parshvanath Jain Temple, isSacredHillTemple, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSacredHillTemple Context triple: [Parshvanath Jain Temple, isSacredHillTemple, true]
-
A.
hillTemple
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
B.
sacredHill
chosen
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
C.
isNumberedTempleOf
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
D.
AtsutaShrineIs
Indicates that something has the status, identity, or defining characteristics of Atsuta Shrine.
-
E.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574c8a248190bf5eef5be78381fd |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.