Triple
T16474549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Shaw |
E400153
|
entity |
| Predicate | livesInHousehold |
P86281
|
FINISHED |
| Object | Shaw household |
—
|
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: Shaw household | Statement: [Mrs. Shaw, livesInHousehold, Shaw household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInHousehold Context triple: [Mrs. Shaw, livesInHousehold, Shaw household]
-
A.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
B.
hasHouseholdMember
chosen
Indicates that one entity is a member of the same household as another entity.
-
C.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
D.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
-
E.
livedWith
Indicates that two entities shared the same residence or household for a period of time.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32dd32e048190a9eadd32d6b9374c |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.