Triple
T4882509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuktidipika |
E109361
|
entity |
| Predicate | addressesOpponent |
P265
|
FINISHED |
| Object | Buddhist philosophical positions |
—
|
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: Buddhist philosophical positions | Statement: [Yuktidipika, addressesOpponent, Buddhist philosophical positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesOpponent Context triple: [Yuktidipika, addressesOpponent, Buddhist philosophical positions]
-
A.
addresses
chosen
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
B.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
C.
invitedOpponents
Indicates that one entity extended an invitation to another entity specifically in the context of being opponents, such as in a match, contest, or competitive event.
-
D.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
E.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddfff0c81908fb148a6f6508334 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.