Triple
T23149059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman census |
E578271
|
entity |
| Predicate | ceremonialConclusion |
P151116
|
FINISHED |
| Object | lustrum purification 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: lustrum purification ceremony | Statement: [Roman census, ceremonialConclusion, lustrum purification ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialConclusion Context triple: [Roman census, ceremonialConclusion, lustrum purification ceremony]
-
A.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
B.
ceremonialLife
Indicates involvement in or association with formal rituals, traditions, or ceremonial practices within a social or cultural context.
-
C.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
D.
ceremonyState
Indicates the current status or phase of a ceremony within its overall lifecycle.
-
E.
ceremonialIssue
Indicates a formal act of presenting or conferring something (such as a document, item, or status) in a ceremonial or ritualized context.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:01 p.m.