Triple
T17952588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaudapada |
E448867
|
entity |
| Predicate | inDialogueWithTradition |
P68934
|
FINISHED |
| Object | Buddhism |
—
|
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: Buddhism | Statement: [Gaudapada, inDialogueWithTradition, Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inDialogueWithTradition Context triple: [Gaudapada, inDialogueWithTradition, Buddhism]
-
A.
inLaterTradition
Indicates that something is interpreted, developed, or regarded in a particular way within subsequent or later traditions compared to its original context.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
linkedToTradition
chosen
Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
-
D.
modernTradition
Indicates a relationship where a practice or custom is recognized as a contemporary development that functions like a tradition within a culture or group.
-
E.
influencedTradition
Indicates that one entity has had a shaping or guiding effect on the development, practices, or values of a particular tradition.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afad61f481908b34cd24de88983c |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.