Triple
T18450840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Rostova |
E450775
|
entity |
| Predicate | maritalStatusInNarrative |
P20884
|
FINISHED |
| Object | married |
—
|
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: married | Statement: [Vera Rostova, maritalStatusInNarrative, married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusInNarrative Context triple: [Vera Rostova, maritalStatusInNarrative, married]
-
A.
marital status
chosen
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
B.
maritalStatusClaimed
Indicates that an entity has asserted or reported a particular marital status, regardless of whether it is verified or legally confirmed.
-
C.
characterMaritalHistory
Indicates a relationship that records the sequence of a character’s past and present marital relationships, including spouses and relevant time periods.
-
D.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
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.
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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52648476c8190a5d8c3297d836f62 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.