Triple
T32627304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guhyasamāja |
E834092
|
entity |
| Predicate | keyCommentator |
P174948
|
FINISHED |
| Object | Nāgārjuna |
—
|
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: Nāgārjuna | Statement: [Guhyasamāja, keyCommentator, Nāgārjuna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCommentator Context triple: [Guhyasamāja, keyCommentator, Nāgārjuna]
-
A.
coCommentatorWith
Indicates that two individuals serve together as commentators on the same event, program, or broadcast.
-
B.
commentator
Indicates that an entity provides spoken or written real-time explanation, analysis, or opinion about an event, action, or content involving another entity.
-
C.
commentatorCountry
Indicates the country with which a commentator is associated, such as their nationality or the nation they represent.
-
D.
sportCommentated
Indicates that one entity provides live or recorded commentary on a sporting event involving another entity.
-
E.
usesCommentaryTeamsOf
Indicates that one entity employs or relies on the commentary teams associated with another entity for coverage or presentation.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 1:06 a.m.