Triple
T19316439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihaspati |
E483109
|
entity |
| Predicate | teacherOf |
P48
|
FINISHED |
| Object | devas |
—
|
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: devas | Statement: [Brihaspati, teacherOf, devas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: devas Context triple: [Brihaspati, teacherOf, devas]
-
A.
Devas
chosen
The Devas are celestial gods in Hindu mythology who play pivotal roles in the cosmic order and divine interventions depicted throughout the Ramayana.
-
B.
daevas
Daevas are malevolent supernatural beings or demons in Zoroastrianism, representing chaos and falsehood in opposition to the benevolent divine entities.
-
C.
Deva
Deva is a prominent Indian film music composer best known for his prolific work in Tamil cinema during the 1990s and early 2000s.
-
D.
Deva
Deva is the Roman-era name for the ancient fortress and settlement that later became the modern English city of Chester.
-
E.
Deva
Deva is a city in western Romania known for its historic fortress and location near the Mureș River in Transylvania.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d843640819089ff3738aae29eb1 |
completed | April 20, 2026, 11:27 a.m. |
Created at: April 10, 2026, 1:32 p.m.