Triple
T28662945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galli priests |
E725514
|
entity |
| Predicate | associatedRitualDay |
P180539
|
FINISHED |
| Object | Day of Blood |
E725512
|
NE 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: Day of Blood | Statement: [Galli priests, associatedRitualDay, Day of Blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRitualDay Context triple: [Galli priests, associatedRitualDay, Day of Blood]
-
A.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
B.
hasRitualDay
chosen
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
-
C.
relatedRitual
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
D.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
E.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
- F. None of above.
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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1cc393cf908190a936b23087af8f2a |
completed | May 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: April 28, 2026, 4:59 a.m.