Triple
T30625049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaivasvata Manvantara |
E779552
|
entity |
| Predicate | hasManu |
P200962
|
FINISHED |
| Object | Vaivasvata Manu |
—
|
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: Vaivasvata Manu | Statement: [Vaivasvata Manvantara, hasManu, Vaivasvata Manu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManu Context triple: [Vaivasvata Manvantara, hasManu, Vaivasvata Manu]
-
A.
hasManual
Indicates that an entity is associated with a manual that provides instructions or documentation for it.
-
B.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
-
C.
hasRuku
Indicates that an entity performs, contains, or is associated with a ruku (the bowing posture/section) within a prayer or recitation structure.
-
D.
hasMaar
Indicates that one entity possesses or contains a maar, i.e., a volcanic crater typically formed by explosive interaction between magma and groundwater.
-
E.
hasMenuCharacteristic
Indicates that a menu possesses a specific characteristic, feature, or attribute.
- F. None of above. chosen
Provenance (4 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: April 29, 2026, 8:27 p.m.