Triple
T19652151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govinda |
E471840
|
entity |
| Predicate | titleInScripture |
P15922
|
FINISHED |
| Object | used as a name of Krishna in the Bhagavad Gita commentary traditions |
—
|
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: used as a name of Krishna in the Bhagavad Gita commentary traditions | Statement: [Govinda, titleInScripture, used as a name of Krishna in the Bhagavad Gita commentary traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInScripture Context triple: [Govinda, titleInScripture, used as a name of Krishna in the Bhagavad Gita commentary traditions]
-
A.
keyBiblicalTitle
Indicates that one entity is a primary or authoritative biblical title or designation for another entity.
-
B.
titleInLatinScript
Indicates that the title of an entity is written or represented using a Latin-based writing system.
-
C.
titles
chosen
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
D.
scriptOfTitle
Indicates that a script (e.g., a written work or screenplay) is associated with or belongs to a particular titled work.
-
E.
titleOfBook
Indicates that one entity is the title assigned to a particular book.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64141f61c819098fe148581fb1747 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.