Triple
T32469023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aunt Sarah |
E829792
|
entity |
| Predicate | householdAuthorityOver |
P133423
|
FINISHED |
| Object | Lady’s home |
—
|
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: Lady’s home | Statement: [Aunt Sarah, householdAuthorityOver, Lady’s home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdAuthorityOver Context triple: [Aunt Sarah, householdAuthorityOver, Lady’s home]
-
A.
familyAuthority
chosen
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
-
B.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
C.
isHouseholdOf
Indicates that one entity functions as the household to which another entity belongs or is associated.
-
D.
familyRule
Indicates a rule, norm, or guideline that governs relationships or behavior within a family context.
-
E.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 12:57 a.m.