Triple
T26263206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marapu ceremonies |
E656907
|
entity |
| Predicate | lifeCycleEvent |
P160176
|
FINISHED |
| Object | birth |
—
|
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: birth | Statement: [Marapu ceremonies, lifeCycleEvent, birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeCycleEvent Context triple: [Marapu ceremonies, lifeCycleEvent, birth]
-
A.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
B.
lifeCycleStructure
Indicates the structural pattern or organization of stages and transitions that make up an entity’s life cycle.
-
C.
brandLifecycleEvent
Indicates an event or change occurring at a specific stage in the lifecycle of a brand, such as its creation, modification, rebranding, or retirement.
-
D.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
E.
lifeCycleRole
Indicates the role an entity plays within a defined life cycle or process stage, such as its function or status at that point in the sequence.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e022a5881908a4582d8d9cbbb38 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:10 p.m.