Triple
T36064397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansi Ganga |
E1043178
|
entity |
| Predicate | hasTempleOnBank |
P8340
|
FINISHED |
| Object | Mansi Ganga temples complex |
—
|
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: Mansi Ganga temples complex | Statement: [Mansi Ganga, hasTempleOnBank, Mansi Ganga temples complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleOnBank Context triple: [Mansi Ganga, hasTempleOnBank, Mansi Ganga temples complex]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
C.
hasLandmarkOnBank
chosen
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
D.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
-
E.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:08 p.m.