Triple
T29616362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindus |
E754874
|
entity |
| Predicate | observesLifeCycleRite |
P20067
|
FINISHED |
| Object | namakarana |
—
|
NE NERFINISHED |
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: namakarana | Statement: [Hindus, observesLifeCycleRite, namakarana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesLifeCycleRite Context triple: [Hindus, observesLifeCycleRite, namakarana]
-
A.
lifeCycleEvent
Indicates an event or transition occurring at a particular stage within an entity's overall life cycle.
-
B.
observedInRite
chosen
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
C.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
D.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
E.
coversLifecycleStage
Indicates that one entity includes, addresses, or spans a particular stage within a defined lifecycle.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 6:31 p.m.