Triple
T19056898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santoshi Mata |
E466420
|
entity |
| Predicate | vowPractice |
P134928
|
FINISHED |
| Object | fasting on Fridays |
—
|
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: fasting on Fridays | Statement: [Santoshi Mata, vowPractice, fasting on Fridays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowPractice Context triple: [Santoshi Mata, vowPractice, fasting on Fridays]
-
A.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
-
B.
vowResult
Indicates that a vow or solemn promise leads to, results in, or is fulfilled by a particular outcome or state.
-
C.
vowelPlacement
Indicates the relative position or arrangement of vowel sounds within a linguistic unit, such as a word or syllable.
-
D.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
E.
keyVow
Indicates a formal promise or commitment that is central or essential to an agreement, relationship, or situation.
- F. None of above. chosen
Provenance (4 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc067f788190b3b149dfee370435 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.