Triple
T26384461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radamès |
E663237
|
entity |
| Predicate | fatherInLawInPlot |
P160583
|
FINISHED |
| Object | Amonasro |
—
|
NE NERFINISHED |
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: Amonasro | Statement: [Radamès, fatherInLawInPlot, Amonasro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherInLawInPlot Context triple: [Radamès, fatherInLawInPlot, Amonasro]
-
A.
fatherInLaw
Indicates a relationship where one person is the father of another person's spouse or the spouse of someone's parent.
-
B.
possibleFatherInLaw
Indicates that one person is a potential or candidate father-in-law of another, typically as the (possible) father of that person’s spouse or prospective spouse.
-
C.
futureFatherInLaw
Indicates that one person is the father of another person's future spouse, i.e., will become their father-in-law through an anticipated marriage.
-
D.
fatherInLawAlsoKnownAs
Indicates that one person is the father-in-law of another and is also known by an alternative name or alias.
-
E.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610784f7481908cc17baeac8a23e4 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 11:21 p.m.