Triple
T37736162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Truths doctrine |
E940281
|
entity |
| Predicate | expoundedIn |
P142360
|
FINISHED |
| Object | Mūlamadhyamakakārikā |
—
|
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: Mūlamadhyamakakārikā | Statement: [Two Truths doctrine, expoundedIn, Mūlamadhyamakakārikā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expoundedIn Context triple: [Two Truths doctrine, expoundedIn, Mūlamadhyamakakārikā]
-
A.
mainlyExpoundedIn
Indicates that the primary or most detailed explanation or treatment of something is found in a particular source or work.
-
B.
alsoExpressedIn
Indicates that something which is expressed in one context, medium, or entity is likewise expressed in another.
-
C.
expressedOn
Indicates that something (such as a feature, marker, or characteristic) is present or manifested on a particular entity or surface.
-
D.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
E.
providesExpositionAbout
chosen
Indicates that one entity offers explanatory or background information clarifying or elaborating on 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.