Triple
T32851498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khedrup Je |
E840263
|
entity |
| Predicate | wroteCommentariesOn |
P22246
|
FINISHED |
| Object | Je Tsongkhapa’s works |
—
|
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: Je Tsongkhapa’s works | Statement: [Khedrup Je, wroteCommentariesOn, Je Tsongkhapa’s works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteCommentariesOn Context triple: [Khedrup Je, wroteCommentariesOn, Je Tsongkhapa’s works]
-
A.
hasCommentaryOn
chosen
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
B.
commentaryOn
Indicates that one entity provides evaluative or explanatory remarks about another entity, such as a work, event, or statement.
-
C.
commentarialTraditionOn
Indicates that a particular commentarial tradition is directed toward, or focused on interpreting, a specific text, idea, or subject.
-
D.
commentaryWorkFor
Indicates that one entity performs commentary or analysis work on behalf of, or under employment/contract with, another entity.
-
E.
commentatedFor
Indicates that one entity provided live or recorded commentary or analysis for an event, performance, or broadcast on behalf of another entity (such as an organization, channel, or client).
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce786af4819082f159abf7bef62c |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.