Triple
T5579031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astraeus |
E146593
|
entity |
| Predicate | spouseRoleRelation |
P33561
|
FINISHED |
| Object | dawn (Eos) and dusk (Astraeus) as complementary deities |
—
|
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: dawn (Eos) and dusk (Astraeus) as complementary deities | Statement: [Astraeus, spouseRoleRelation, dawn (Eos) and dusk (Astraeus) as complementary deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseRoleRelation Context triple: [Astraeus, spouseRoleRelation, dawn (Eos) and dusk (Astraeus) as complementary deities]
-
A.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
B.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
C.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
D.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
E.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0206bfea08190aa2c8df9f88013ac |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.