Triple
T32000047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen Belluschi |
E817098
|
entity |
| Predicate | partnerInSocialLifeOf |
P179068
|
FINISHED |
| Object | Pietro Belluschi |
—
|
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: Pietro Belluschi | Statement: [Helen Belluschi, partnerInSocialLifeOf, Pietro Belluschi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInSocialLifeOf Context triple: [Helen Belluschi, partnerInSocialLifeOf, Pietro Belluschi]
-
A.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
B.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
C.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
-
D.
partnerInCareerOf
Indicates a relationship where one entity is a professional or career partner of another, collaborating or sharing a joint career path or venture.
-
E.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: May 1, 2026, 12:14 a.m.