Triple
T23833341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovey Howell |
E589572
|
entity |
| Predicate | fictionalMaritalRole |
P95303
|
FINISHED |
| Object | millionaire's wife |
—
|
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: millionaire's wife | Statement: [Lovey Howell, fictionalMaritalRole, millionaire's wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalMaritalRole Context triple: [Lovey Howell, fictionalMaritalRole, millionaire's wife]
-
A.
fictionalMaritalStatus
Indicates that an entity has a marital status that exists only within a fictional, narrative, or hypothetical context rather than in real life.
-
B.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
C.
fictionalStepmother
Indicates a stepmother relationship that exists only within a fictional or narrative context.
-
D.
afterMarriageRole
chosen
Indicates the role or status an entity assumes following a marriage event.
-
E.
fictionalGender
Indicates that one entity has a gender identity or classification that exists only within a fictional or imaginary context.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f7aa488190b1bc5cab77a11123 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:06 p.m.