Triple
T38439618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankie Bergstein |
E906450
|
entity |
| Predicate | maritalStatusAfterRevelation |
P191158
|
FINISHED |
| Object | separated |
—
|
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: separated | Statement: [Frankie Bergstein, maritalStatusAfterRevelation, separated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusAfterRevelation Context triple: [Frankie Bergstein, maritalStatusAfterRevelation, separated]
-
A.
socialStatusAfterMarriage
Indicates the social status an individual holds as a result of, or following, their marriage.
-
B.
maritalStatusInDisguise
Indicates that an entity’s true marital status is being concealed or misrepresented, typically appearing different from what it actually is.
-
C.
hasMaritalStatusAfterFirstMarriage
Indicates that an entity’s marital status at a given time is the one it holds after its first marriage has occurred.
-
D.
maritalStatusBeforeRenunciation
Indicates the marital status a person had prior to formally renouncing a role, status, or affiliation.
-
E.
hasMaritalStatusAtEnd
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:31 p.m.