Triple
T5682698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupercalia |
E125233
|
entity |
| Predicate | suppression |
P10731
|
FINISHED |
| Object | late 5th century CE |
—
|
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: late 5th century CE | Statement: [Lupercalia, suppression, late 5th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppression Context triple: [Lupercalia, suppression, late 5th century CE]
-
A.
suppressedDuring
chosen
Indicates that one event, action, or state is actively prevented, inhibited, or held back while another specified event, condition, or time period is occurring.
-
B.
suppressedFollowing
Indicates that one entity’s act of following another has been intentionally hidden, blocked, or not allowed to occur.
-
C.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of another entity.
-
D.
reasonForSuppression
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
-
E.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.