Triple
T30892725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Lacey family |
E786944
|
entity |
| Predicate | includesFutureDaughterInLaw |
P144372
|
FINISHED |
| Object | Safie |
—
|
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: Safie | Statement: [De Lacey family, includesFutureDaughterInLaw, Safie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFutureDaughterInLaw Context triple: [De Lacey family, includesFutureDaughterInLaw, Safie]
-
A.
isProspectiveDaughterInLawOf
chosen
Indicates that one person is expected or intended to become the daughter-in-law of another person, typically through a planned or anticipated marriage to that person's child.
-
B.
daughterInLaw
Indicates a relationship where one person is the wife of another person's child.
-
C.
futureMotherInLaw
Indicates a relationship where one person is the mother of another person's future spouse, i.e., the mother-in-law in a planned or anticipated marriage.
-
D.
granddaughterInLaw
Indicates that one person is the wife of another person's grandchild.
-
E.
sonInLaw
Indicates that one person is the husband of another person's child.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: April 29, 2026, 8:49 p.m.