Triple
T20342811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hare Krishna maha-mantra |
E495782
|
entity |
| Predicate | invokesName |
P139761
|
FINISHED |
| Object | Hare |
—
|
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: Hare | Statement: [Hare Krishna maha-mantra, invokesName, Hare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokesName Context triple: [Hare Krishna maha-mantra, invokesName, Hare]
-
A.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
B.
nameOf
Indicates that one entity is the name or designation of another entity.
-
C.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
D.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67836b72081908be65115abdb37bf |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:24 a.m.