Triple
T29021636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Vesta |
E737463
|
entity |
| Predicate | finalSuppression |
P117119
|
FINISHED |
| Object | reign of Theodosius I |
—
|
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: reign of Theodosius I | Statement: [cult of Vesta, finalSuppression, reign of Theodosius I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSuppression Context triple: [cult of Vesta, finalSuppression, reign of Theodosius I]
-
A.
typeOfSuppression
Indicates the specific manner or mechanism by which something is suppressed, inhibited, or prevented from occurring or being expressed.
-
B.
suppressedOn
Indicates that one entity is intentionally prevented, hidden, or blocked from being shown, executed, or taking effect in the context of another entity.
-
C.
wasSuppressedBy
Indicates that an action, event, or expression was actively prevented, restrained, or silenced by another agent or force.
-
D.
finalService
Indicates that a service represents the last or concluding service in a sequence, process, or lifecycle.
-
E.
orderedSuppressionOf
chosen
Indicates that one entity has formally directed or mandated the suppression, restriction, or silencing of another entity or its actions.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 28, 2026, 9:49 a.m.