Triple
T3322136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pranami religious practices |
E69818
|
entity |
| Predicate | dailyPractice |
P47276
|
FINISHED |
| Object | personal prayer |
—
|
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: personal prayer | Statement: [Pranami religious practices, dailyPractice, personal prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyPractice Context triple: [Pranami religious practices, dailyPractice, personal prayer]
-
A.
functionToday
Indicates that a function or role is being performed or is in effect on the current day.
-
B.
memorizationPractice
Indicates engaging in activities or exercises specifically intended to commit information to memory or strengthen recall.
-
C.
nameDayPractice
Indicates the customary observance or celebration associated with a person’s name day.
-
D.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
-
E.
challengedPractice
Indicates that one entity has questioned, disputed, or formally opposed the validity, appropriateness, or continuation of another entity’s practice or procedure.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13d13a88190828d9a03fd0865ce |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.