Triple
T6262843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavanputra |
E140341
|
entity |
| Predicate | honorsDeityAspect |
P60804
|
FINISHED |
| Object | Hanuman as son of Vayu |
—
|
LITERAL 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: Hanuman as son of Vayu | Statement: [Pavanputra, honorsDeityAspect, Hanuman as son of Vayu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsDeityAspect Context triple: [Pavanputra, honorsDeityAspect, Hanuman as son of Vayu]
-
A.
honorsAspectOf
chosen
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
B.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
C.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
D.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.