Triple
T8565449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya Kund |
E202789
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Surya |
E102111
|
NE 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: Surya | Statement: [Surya Kund, namedAfter, Surya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Surya Context triple: [Surya Kund, namedAfter, Surya]
-
A.
Surya
chosen
Surya is the Hindu sun god revered as a major solar deity associated with light, power, and vitality.
-
B.
Inti
Inti is the Incan sun god, revered as a principal deity associated with royal power, agriculture, and the cosmic order.
-
C.
Saha
Saha is a surname most notably associated with Indian astrophysicist Meghnad Saha, known for the Saha ionization equation in stellar astrophysics.
-
D.
Saha
Saha is a small town in the Ambala district of the northern Indian state of Haryana, known primarily as a local commercial and transport hub for surrounding rural areas.
-
E.
Surya Kund
Surya Kund is a famous natural hot water spring near the Yamunotri temple in Uttarakhand, India, where pilgrims traditionally cook offerings and perform ritual baths.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d2331881909d92ddde90f580e9 |
completed | March 31, 2026, 3:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc72d8c08190b5e063e6de2bbdd2 |
completed | April 2, 2026, 8:07 p.m. |
Created at: March 30, 2026, 6:20 p.m.