Triple
T5200382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vayu |
E117377
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | Devas |
E109926
|
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: Devas | Statement: [Vayu, memberOf, Devas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Devas Context triple: [Vayu, memberOf, 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.
Deva
Deva is the Roman-era name for the ancient fortress and settlement that later became the modern English city of Chester.
-
C.
Deva
Deva is a city in western Romania known for its historic fortress and location near the Mureș River in Transylvania.
-
D.
Rakshasas
Rakshasas are powerful, shape-shifting demon beings from Hindu mythology, often portrayed as malevolent antagonists in epics like the Ramayana.
-
E.
Vanaras
Vanaras are a race of monkey-like humanoid warriors in the Indian epic Ramayana, renowned for their strength, agility, and pivotal role in aiding Rama in his quest to rescue Sita.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a209d7c81908fa0d3bf2c482a34 |
completed | March 20, 2026, 4:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee0a37d8c8190842de23da26dd2cb |
completed | March 21, 2026, 6:17 p.m. |
Created at: March 20, 2026, 1:47 p.m.