Triple
T32541425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feriae Latinae |
E831721
|
entity |
| Predicate | sacrificeRecipient |
P49011
|
FINISHED |
| Object | Jupiter Latiaris |
—
|
NE NERFINISHED |
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: Jupiter Latiaris | Statement: [Feriae Latinae, sacrificeRecipient, Jupiter Latiaris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificeRecipient Context triple: [Feriae Latinae, sacrificeRecipient, Jupiter Latiaris]
-
A.
sacrificedTo
chosen
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
B.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
C.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
D.
sacrificialMedium
Indicates that one entity serves as the medium or vehicle through which another entity is sacrificed or offered.
-
E.
offeredSacrificeOn
Indicates that one entity performed a sacrificial offering upon or at another entity (such as an altar, location, or occasion).
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57f14348190a0e2b98597e5ba25 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.