Triple
T31637104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoschedé family |
E807340
|
entity |
| Predicate | mergedHouseholdWith |
P89372
|
FINISHED |
| Object | Monet family |
—
|
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: Monet family | Statement: [Hoschedé family, mergedHouseholdWith, Monet family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedHouseholdWith Context triple: [Hoschedé family, mergedHouseholdWith, Monet family]
-
A.
hadHouseholds
Indicates that an entity possessed or was associated with one or more households during a specified time or context.
-
B.
sharesHouseholdWith
chosen
Indicates that two entities live together in the same household as co-residents.
-
C.
unionFamily
Indicates a familial relationship formed through marriage or civil union, rather than by blood or adoption.
-
D.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
E.
someMembersMergedWith
Indicates that a subset of members from one group combined or integrated with members of another group to form a unified entity or subgroup.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:47 p.m.