Triple
T28143074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindsay Boxer |
E714401
|
entity |
| Predicate | appearsInGenreSeries |
P26455
|
FINISHED |
| Object | Women’s Murder Club crime-thriller novels |
—
|
NE NERFINISHED |
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: Women’s Murder Club crime-thriller novels | Statement: [Lindsay Boxer, appearsInGenreSeries, Women’s Murder Club crime-thriller novels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInGenreSeries Context triple: [Lindsay Boxer, appearsInGenreSeries, Women’s Murder Club crime-thriller novels]
-
A.
appearsInSeries
chosen
Indicates that an entity is featured or occurs within a particular series.
-
B.
appearsInSeriesBy
Indicates that one entity (such as a work or character) is featured within a series that is created, authored, or produced by another entity.
-
C.
hasGenreInSeries
Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
-
D.
notableGenreSeries
Indicates that a series is notably associated with or recognized for a particular genre.
-
E.
coveredInGenre
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 9:54 p.m.