Triple
T34022051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonagiri Jain temples, Madhya Pradesh |
E872405
|
entity |
| Predicate | hasTempleNumber |
P113872
|
FINISHED |
| Object | Temple No. 57 |
—
|
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: Temple No. 57 | Statement: [Sonagiri Jain temples, Madhya Pradesh, hasTempleNumber, Temple No. 57]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleNumber Context triple: [Sonagiri Jain temples, Madhya Pradesh, hasTempleNumber, Temple No. 57]
-
A.
isNumberedTempleOf
chosen
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
B.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
-
C.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
D.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
E.
hasTempleCode
Indicates that an entity is associated with a specific temple identification code.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:51 a.m.