Triple
T19708166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushti-margiya granthas |
E473268
|
entity |
| Predicate | viewOnPath |
P43388
|
FINISHED |
| Object | reject austerity-centered paths |
—
|
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: reject austerity-centered paths | Statement: [Pushti-margiya granthas, viewOnPath, reject austerity-centered paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnPath Context triple: [Pushti-margiya granthas, viewOnPath, reject austerity-centered paths]
-
A.
viewOnObject
Indicates that one entity directs its visual attention toward or observes another entity as an object of viewing.
-
B.
viewOnImages
Indicates that one entity views or displays another entity specifically in the form of images.
-
C.
viewOnHereafter
Indicates a subject’s beliefs, opinions, or perspective regarding the afterlife or what happens after death.
-
D.
viewOnValue
chosen
Indicates a relationship where one entity holds or expresses a particular perspective, opinion, or stance regarding a specific value or principle.
-
E.
viewIs
Indicates that one entity is a visual representation or perspective of 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bc754481908bdf5bfad069aec8 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.