Triple
T32739137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Svevo |
E837171
|
entity |
| Predicate | hadRelationshipErasedWith |
P174750
|
FINISHED |
| Object | Howard Mierzwiak |
—
|
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: Howard Mierzwiak | Statement: [Mary Svevo, hadRelationshipErasedWith, Howard Mierzwiak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRelationshipErasedWith Context triple: [Mary Svevo, hadRelationshipErasedWith, Howard Mierzwiak]
-
A.
laterRelationshipWith
Indicates that one entity has a relationship with another that occurs at a later time relative to some reference point or prior relationship.
-
B.
hasAllegedRelationshipWith
Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
-
C.
formerRelationshipStatus
Indicates that a relationship between entities existed in the past but no longer holds in the present.
-
D.
relationshipEnd
Indicates that a previously existing relationship between entities has been terminated or has come to an end.
-
E.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c906d54881909573f2d82ecd7ddd |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c5fa10dc8190b2c06e4c701bd246 |
completed | May 3, 2026, 3:50 a.m. |
Created at: May 1, 2026, 1:12 a.m.