Triple
T29429998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pilgrimage to Hierapolis |
E746400
|
entity |
| Predicate | ritualOfferingType |
P36512
|
FINISHED |
| Object | animal sacrifices |
—
|
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: animal sacrifices | Statement: [pilgrimage to Hierapolis, ritualOfferingType, animal sacrifices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualOfferingType Context triple: [pilgrimage to Hierapolis, ritualOfferingType, animal sacrifices]
-
A.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
B.
isOftenOfferedToDeity
Indicates that something is frequently presented or dedicated as an offering to a deity.
-
C.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
D.
sacrificeType
chosen
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
E.
ritualSpecialization
Indicates a relationship where an entity is specifically focused on, trained in, or primarily responsible for performing a particular type of ritual or set of ritual practices.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66ac8bb9081908af9b31ab052956d |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:12 p.m.