Triple
T20305996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjaneya |
E505609
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | Vanara |
—
|
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: Vanara | Statement: [Anjaneya, memberOf, Vanara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vanara Context triple: [Anjaneya, memberOf, Vanara]
-
A.
Vanara
chosen
Vanara are a race of monkey-like humanoid beings in Hindu mythology, most prominently featured as the allies of Lord Rama in the epic Ramayana.
-
B.
Phulparas
Phulparas is a town in the Madhubani district of Bihar, India, known for its role as a local administrative and market center in the region.
-
C.
Vanayu
Vanayu is a relatively obscure figure in Hindu mythology, known primarily as one of the sons of the legendary king Pururavas.
-
D.
Kunjara
Kunjara is an alternative name for the Fur language spoken by the Fur people of western Sudan.
-
E.
Annamocarya
Annamocarya is a genus of flowering trees in the walnut family known for its large, nut-bearing species native to parts of Asia.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773f8f688190b616f972b9bbb28e |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:18 a.m.