Triple
T16172412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Carneius |
E392470
|
entity |
| Predicate | hasRitualAssociation |
P70955
|
FINISHED |
| Object | camp-like encampments during Carneia |
—
|
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: camp-like encampments during Carneia | Statement: [Apollo Carneius, hasRitualAssociation, camp-like encampments during Carneia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualAssociation Context triple: [Apollo Carneius, hasRitualAssociation, camp-like encampments during Carneia]
-
A.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
B.
hasRituals
chosen
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
D.
hasRitualRule
Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
-
E.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb88c948190a1d8b5518694ad53 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.