Triple
T19988018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uttarayan Festival |
E493981
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Surya (Sun god) |
—
|
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: Surya (Sun god) | Statement: [Uttarayan Festival, associatedDeity, Surya (Sun god)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Surya (Sun god) Context triple: [Uttarayan Festival, associatedDeity, Surya (Sun god)]
-
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.
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.
-
D.
Vivasvan
Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
-
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 (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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
Created at: April 11, 2026, 3:30 p.m.