Triple
T31645639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigrahavyāvartanī |
E807575
|
entity |
| Predicate | addressesObjectionsFrom |
P174856
|
FINISHED |
| Object | realist Buddhist schools |
—
|
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: realist Buddhist schools | Statement: [Vigrahavyāvartanī, addressesObjectionsFrom, realist Buddhist schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesObjectionsFrom Context triple: [Vigrahavyāvartanī, addressesObjectionsFrom, realist Buddhist schools]
-
A.
addressesCriticismFrom
chosen
Indicates that one party responds to, engages with, or attempts to answer criticism originating from another party.
-
B.
accusationsAddressed
Indicates that previously made accusations have been responded to, dealt with, or otherwise handled by a relevant party.
-
C.
concernsAddressed
Indicates that specific issues, worries, or topics raised by one party have been acknowledged and dealt with by another party.
-
D.
addressesIssue
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
E.
arguedWith
Indicates that one entity engaged in a verbal dispute or disagreement with another entity.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 30, 2026, 10:51 p.m.