Triple
T9716862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vestal Virgins |
E235162
|
entity |
| Predicate | punishmentForNeglectingFire |
P58903
|
FINISHED |
| Object | scourging |
—
|
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: scourging | Statement: [Vestal Virgins, punishmentForNeglectingFire, scourging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishmentForNeglectingFire Context triple: [Vestal Virgins, punishmentForNeglectingFire, scourging]
-
A.
fireRegulation
Indicates rules or requirements governing the prevention, control, and safe management of fire-related risks and activities.
-
B.
neglects
Indicates a relationship where one party fails to give appropriate attention, care, or consideration to another party or responsibility.
-
C.
reasonForPunishment
chosen
Indicates that one entity is the cause, justification, or grounds for another entity receiving a punishment.
-
D.
fireProblemSince
Indicates that a fire-related problem has been occurring or has been present since a specific point in time.
-
E.
punishedBy
Indicates that an entity receives punishment administered by another entity.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3d75e08190b4d86363595bd40d |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:20 p.m.