Triple
T18096965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keller family |
E433113
|
entity |
| Predicate | familyHomeUse |
P65667
|
FINISHED |
| Object | historic house museum |
—
|
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: historic house museum | Statement: [Keller family, familyHomeUse, historic house museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyHomeUse Context triple: [Keller family, familyHomeUse, historic house museum]
-
A.
houseUse
chosen
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
-
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.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
D.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
E.
householdPractice
Indicates a relationship where an entity engages in or carries out a particular practice, behavior, or routine within the context of a household.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1de6f48190a3fefd02a4b2ab58 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.