Triple
T20566938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Rituals |
E504988
|
entity |
| Predicate | describesRite |
P28133
|
FINISHED |
| Object | capping ceremony |
—
|
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: capping ceremony | Statement: [Family Rituals, describesRite, capping ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesRite Context triple: [Family Rituals, describesRite, capping ceremony]
-
A.
containsRite
chosen
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
B.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
C.
ritualCharacteristics
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
D.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
E.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a33f7c8190966da03528dfe8aa |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.