Triple
T19698893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijaya bow |
E473038
|
entity |
| Predicate | creator |
P184
|
FINISHED |
| Object | Vishvakarma |
—
|
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: Vishvakarma | Statement: [Vijaya bow, creator, Vishvakarma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vishvakarma Context triple: [Vijaya bow, creator, Vishvakarma]
-
A.
divine architect Vishvakarma
chosen
Vishvakarma is the divine architect and craftsman of the gods in Hindu mythology, revered as the celestial engineer who designs and constructs heavenly cities, weapons, and palaces.
-
B.
Daksha
Daksha was a ruler who succeeded King Balitung in the line of Mataram (Medang) monarchs in early medieval Java.
-
C.
Daksha
Daksha is a prominent Vedic deity and progenitor figure in Hindu mythology, often associated with creation, ritual order, and the lineage of gods and sages.
-
D.
Prajapati
Prajapati is a taxonomist credited with formally describing and naming the bacterial order Corynebacteriales.
-
E.
Prajapati
Prajapati is a Vedic creator deity associated with the origin, ordering, and procreation of the cosmos in early Hindu tradition.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b426608190a46abec3652a6ca0 |
completed | April 20, 2026, 3:13 p.m. |
Created at: April 10, 2026, 1:46 p.m.