Triple
T19707747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulabharam ritual |
E473258
|
entity |
| Predicate | donationForm |
P117377
|
FINISHED |
| Object | in-kind offerings |
—
|
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: in-kind offerings | Statement: [Tulabharam ritual, donationForm, in-kind offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: donationForm Context triple: [Tulabharam ritual, donationForm, in-kind offerings]
-
A.
donationPlatform
Indicates a relationship where an entity serves as the platform or service through which a donation is made or processed.
-
B.
philanthropicDonation
Indicates that one entity voluntarily gives money, goods, or services to another entity for charitable or public-benefit purposes without expecting direct compensation.
-
C.
donatedWith
chosen
Indicates that an entity made a donation using, accompanied by, or in association with a particular method, item, or context.
-
D.
donationStyle
Indicates the characteristic manner or approach with which a donation is given or carried out.
-
E.
donated
Indicates that one entity voluntarily gave something of value (such as money, goods, or time) to another entity, typically without expecting anything in return.
- 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.