Triple
T11793891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shango festival |
E280455
|
entity |
| Predicate | includesOfferingType |
P34857
|
FINISHED |
| Object | food 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: food offerings | Statement: [Shango festival, includesOfferingType, food offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOfferingType Context triple: [Shango festival, includesOfferingType, food offerings]
-
A.
offeringType
chosen
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
B.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
C.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
D.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
E.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.