Triple
T13032728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhathi Maiya |
E326481
|
entity |
| Predicate | iconographicAssociation |
P49031
|
FINISHED |
| Object | Sun god 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: Sun god Surya | Statement: [Chhathi Maiya, iconographicAssociation, Sun god Surya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sun god Surya Context triple: [Chhathi Maiya, iconographicAssociation, Sun god Surya]
-
A.
Sun God
Sun God is a monumental outdoor sculpture by Niki de Saint Phalle located at the University of California, San Diego, known for its vibrant colors and iconic bird-like form.
-
B.
Surya
chosen
Surya is the Hindu sun god revered as a major solar deity associated with light, power, and vitality.
-
C.
Vivasvan
Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
-
D.
Re (sun god)
Re is the ancient Egyptian sun god, a major creator deity and king of the gods who traveled across the sky by day and through the underworld by night.
-
E.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efe72348190b52fb4068f5fb829 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbcd25108190a6c4a129cde81534 |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:54 p.m.