Triple
T8791105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iphigenia |
E209166
|
entity |
| Predicate | causeOfNearSacrifice |
P23772
|
FINISHED |
| Object | need for favorable winds to sail to Troy |
—
|
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: need for favorable winds to sail to Troy | Statement: [Iphigenia, causeOfNearSacrifice, need for favorable winds to sail to Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfNearSacrifice Context triple: [Iphigenia, causeOfNearSacrifice, need for favorable winds to sail to Troy]
-
A.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
B.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
C.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
D.
reasonForTribute
chosen
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
-
E.
viewOfSacrifices
Indicates a perspective, attitude, or evaluative stance that an entity holds toward sacrifices or acts of sacrificing.
- 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_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. |
Created at: March 30, 2026, 6:43 p.m.