Triple
T21865266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larentalia |
E539867
|
entity |
| Predicate | typeOfRite |
P76648
|
FINISHED |
| Object | commemorative rite for the dead |
—
|
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: commemorative rite for the dead | Statement: [Larentalia, typeOfRite, commemorative rite for the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRite Context triple: [Larentalia, typeOfRite, commemorative rite for the dead]
-
A.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
B.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
C.
containsRite
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
D.
ritualCategory
chosen
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
E.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63e70c08190a9ba90c47c4060d4 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.