Triple
T25255268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Jefferson |
E633152
|
entity |
| Predicate | householdAssociation |
P4085
|
FINISHED |
| Object | Jefferson 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: Jefferson family | Statement: [Mother Jefferson, householdAssociation, Jefferson family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdAssociation Context triple: [Mother Jefferson, householdAssociation, Jefferson family]
-
A.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
B.
sharesHouseholdWith
Indicates that two entities live together in the same household as co-residents.
-
C.
household
chosen
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
D.
homeAssociation
Indicates a relationship where one entity is associated with, belongs to, or is linked as a home or primary place to another entity.
-
E.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:13 p.m.