Triple
T35227075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shashthi Devi |
E1017126
|
entity |
| Predicate | honoredOnOccasion |
P61621
|
FINISHED |
| Object | childbirth ceremonies |
—
|
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: childbirth ceremonies | Statement: [Shashthi Devi, honoredOnOccasion, childbirth ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoredOnOccasion Context triple: [Shashthi Devi, honoredOnOccasion, childbirth ceremonies]
-
A.
honoredOn
chosen
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
B.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
C.
honoureeParticipatedIn
Indicates that the honouree took part in, or was involved in, a specific event, activity, or occasion.
-
D.
grantedOnOccasionOf
Indicates that something (such as a right, benefit, or status) is conferred specifically in connection with, or as a result of, a particular occasion or event.
-
E.
dedicatedOnOccasionOf
Indicates that something (typically a work, object, or event) is formally dedicated in connection with or to commemorate a particular occasion.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.