Triple
T28336526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judith Hellman |
E717688
|
entity |
| Predicate | placeOfSignificantFamilyActivity |
P178030
|
FINISHED |
| Object | San Francisco |
—
|
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: San Francisco | Statement: [Judith Hellman, placeOfSignificantFamilyActivity, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfSignificantFamilyActivity Context triple: [Judith Hellman, placeOfSignificantFamilyActivity, San Francisco]
-
A.
notableFamilyActivity
Indicates that a family is particularly recognized for engaging in a specific activity or set of activities.
-
B.
fieldOfActivityOfFamily
Indicates the domain, profession, or area of activity in which a family is or was primarily engaged.
-
C.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
D.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 12:36 a.m.