Triple
T28314090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broke |
E714082
|
entity |
| Predicate | leadCharacterFamilyStatus |
P80421
|
FINISHED |
| Object | single mother |
—
|
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: single mother | Statement: [Broke, leadCharacterFamilyStatus, single mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCharacterFamilyStatus Context triple: [Broke, leadCharacterFamilyStatus, single mother]
-
A.
protagonistFamilyStatus
chosen
Indicates the familial role or position that a character holds in relation to the story’s protagonist.
-
B.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
familyNameStatus
Indicates the status or condition of a person's family name, such as whether it is current, former, changed, or otherwise designated.
-
D.
notableFamilyStatus
Indicates that an entity holds a distinguished or prominent position or role within a particular family.
-
E.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:42 p.m.