Triple
T18937303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thetis |
E463281
|
entity |
| Predicate | marriedToMortalBecause |
P133869
|
FINISHED |
| Object | Zeus feared prophecy about her son |
—
|
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: Zeus feared prophecy about her son | Statement: [Thetis, marriedToMortalBecause, Zeus feared prophecy about her son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToMortalBecause Context triple: [Thetis, marriedToMortalBecause, Zeus feared prophecy about her son]
-
A.
marriedInAfterlifeTo
Indicates that one entity is joined in marriage to another specifically within an afterlife or post-mortem context.
-
B.
marriedToUntilDeathOfSpouse
Indicates a marital relationship that is intended to remain in effect until the death of one of the spouses.
-
C.
associatedWithMortal
Indicates a relationship where an entity is connected or linked in some way to a mortal being (a being subject to death).
-
D.
marriedToHeiress
Indicates that a person is married to someone who is an heiress.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e8fdb48190ae70cb23c5bc2c97 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.