Triple
T8791128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iphigenia |
E209166
|
entity |
| Predicate | sacrificeSubstituteInSomeVersions |
P85411
|
FINISHED |
| Object | deer |
—
|
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: deer | Statement: [Iphigenia, sacrificeSubstituteInSomeVersions, deer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacrificeSubstituteInSomeVersions Context triple: [Iphigenia, sacrificeSubstituteInSomeVersions, deer]
-
A.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
B.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
C.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
D.
sacrificeAcceptedBy
Indicates that a sacrificial offering made by one entity is received and deemed acceptable by another entity.
-
E.
liturgicalSubstitute
Indicates that one liturgical element, person, or text is used in place of another within a religious rite or ceremony.
- F. None of above. chosen
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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8e6e4881909155c40c52bc082c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:43 p.m.