Triple
T6262830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavanputra |
E140341
|
entity |
| Predicate | appliedTo |
P1129
|
FINISHED |
| Object | monkey-god Hanuman |
E21412
|
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: monkey-god Hanuman | Statement: [Pavanputra, appliedTo, monkey-god Hanuman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: monkey-god Hanuman Context triple: [Pavanputra, appliedTo, monkey-god Hanuman]
-
A.
Hanuman
chosen
Hanuman is a revered Hindu deity known for his immense strength, unwavering devotion to Lord Rama, and central role in the epic Ramayana.
-
B.
Anjaneya
Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
-
C.
Hanuman Pol
Hanuman Pol is one of the main historic entrance gates of Rajasthan’s Kumbhalgarh Fort, serving as a fortified access point and defensive structure.
-
D.
Sugriva
Sugriva is the exiled monkey king in the Hindu epic Ramayana who allies with Rama to defeat the demon king Ravana and reclaim his own throne.
-
E.
Mahākāśyapa
Mahākāśyapa was one of the Buddha’s foremost disciples, revered in early Buddhism and Zen as the primary heir to the Buddha’s teaching and the first patriarch of the Zen lineage.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06387fec0819095b47a37b9402aa9 |
completed | March 22, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c603ee891481909f640f54b70f9d60 |
completed | March 27, 2026, 4:13 a.m. |
Created at: March 22, 2026, 4:25 p.m.