Triple
T21884081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasiphaë |
E540360
|
entity |
| Predicate | causeOfPassion |
P694
|
FINISHED |
| Object | curse by Poseidon |
—
|
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: curse by Poseidon | Statement: [Pasiphaë, causeOfPassion, curse by Poseidon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPassion Context triple: [Pasiphaë, causeOfPassion, curse by Poseidon]
-
A.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
hasPassion
Indicates that one entity feels a strong enthusiasm, interest, or love for another entity, activity, or subject.
-
D.
causeCélèbre
Indicates a relationship where an event, issue, or person becomes widely known and intensely debated or celebrated in public discourse.
-
E.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e9d3508190aadcfcdac0376387 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.