Triple
T20872413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eriphyle |
E513926
|
entity |
| Predicate | spouseAttribute |
P91240
|
FINISHED |
| Object | Amphiaraus foresaw his death in the Theban war |
—
|
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: Amphiaraus foresaw his death in the Theban war | Statement: [Eriphyle, spouseAttribute, Amphiaraus foresaw his death in the Theban war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseAttribute Context triple: [Eriphyle, spouseAttribute, Amphiaraus foresaw his death in the Theban war]
-
A.
spouseCharacteristic
chosen
Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
D.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
-
E.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c465693881909fe4c756ddc4f291 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.