Triple
T20975621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalnath Temple |
E516617
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Mangal |
—
|
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: Mangal | Statement: [Mangalnath Temple, associatedDeity, Mangal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mangal Context triple: [Mangalnath Temple, associatedDeity, Mangal]
-
A.
Mangal
Mangal is a Pashtun tribe traditionally associated with the Karlani tribal confederation in Afghanistan and Pakistan.
-
B.
Mangal
Mangal is a given name most notably borne by Mangal Pandey, an Indian soldier whose actions helped spark the Indian Rebellion of 1857.
-
C.
Mangala
chosen
Mangala is the Hindu deity associated with the planet Mars, symbolizing strength, courage, and martial energy in Vedic astrology.
-
D.
Varuna
Varuna is a large, rapidly rotating trans-Neptunian object in the Kuiper Belt, notable for its elongated shape and classification as a likely dwarf-planet candidate.
-
E.
Varuna
Varuna is an ancient Vedic god primarily associated with cosmic order, moral law, and the waters, often regarded as a sovereign guardian of ṛta (universal order).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba3df2081908c1db5f8610ba43d |
completed | April 21, 2026, 4:23 a.m. |
Created at: April 16, 2026, 1:46 p.m.