Triple
T23653261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Don’t Know How She Does It |
E584223
|
entity |
| Predicate | workLifeConflictCentral |
P153049
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [I Don’t Know How She Does It, workLifeConflictCentral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLifeConflictCentral Context triple: [I Don’t Know How She Does It, workLifeConflictCentral, true]
-
A.
workBasedOnLife
Indicates that a creative work is based on, inspired by, or derived from a particular person's life or life experiences.
-
B.
focusesOnWork
Indicates that an entity directs its attention, effort, or primary activity toward work-related tasks or responsibilities.
-
C.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
D.
work focus
Indicates that an entity’s primary professional attention, effort, or activity is concentrated on a particular subject, task, or area.
-
E.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3599128819092b6a44779889a78 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.