Triple
T32966660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphitruo |
E843388
|
entity |
| Predicate | hasDoubleOfHusband |
P180828
|
FINISHED |
| Object | Jupiter disguised as Amphitryon |
—
|
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: Jupiter disguised as Amphitryon | Statement: [Amphitruo, hasDoubleOfHusband, Jupiter disguised as Amphitryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoubleOfHusband Context triple: [Amphitruo, hasDoubleOfHusband, Jupiter disguised as Amphitryon]
-
A.
spouseInDuo
Indicates that two individuals are spouses who perform or appear together as a duo.
-
B.
hasAnotherWife
Indicates that a person is married to more than one wife, specifying the existence of an additional wife beyond the first.
-
C.
hasSpousePositionInFamily
Indicates that a person’s spouse holds a specific role or position within the family structure.
-
D.
hasNamesakeSpouse
Indicates that one entity has a spouse who shares the same name as another specified entity.
-
E.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: May 1, 2026, 1:21 a.m.