Triple
T29021619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Vesta |
E737463
|
entity |
| Predicate | penaltyForNeglectingFire |
P166283
|
FINISHED |
| Object | corporal punishment of Vestal Virgin |
—
|
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: corporal punishment of Vestal Virgin | Statement: [cult of Vesta, penaltyForNeglectingFire, corporal punishment of Vestal Virgin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyForNeglectingFire Context triple: [cult of Vesta, penaltyForNeglectingFire, corporal punishment of Vestal Virgin]
-
A.
fireRegulation
Indicates rules or requirements governing the prevention, control, and safe management of fire-related risks and activities.
-
B.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
C.
fireProblemSince
Indicates that a fire-related problem has been occurring or has been present since a specific point in time.
-
D.
consequenceOfFire
Indicates that something occurs as a result or outcome of a fire.
-
E.
fireIncidentRelated
Indicates that there is a connection or association between a specific fire incident and another entity, event, or record.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66005ea00819085501231fe82cc5e |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:49 a.m.