Triple
T23197104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Failing |
E579900
|
entity |
| Predicate | isSetInWorkType |
P78942
|
FINISHED |
| Object | English novel |
—
|
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: English novel | Statement: [Mrs. Failing, isSetInWorkType, English novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSetInWorkType Context triple: [Mrs. Failing, isSetInWorkType, English novel]
-
A.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
B.
hasWorkTypeRelation
Indicates a relationship specifying the type or category of work associated with an entity.
-
C.
hasWorkAsSetting
chosen
Indicates that a particular work (such as a story, film, or artwork) takes place in or uses a specified location, time, or environment as its setting.
-
D.
usedInWorkSetIn
Indicates that something (such as an element, motif, or device) is employed within a creative work whose narrative or content is set in a particular place or time.
-
E.
workInSet
Indicates that an entity performs work or has a role within a specified set, group, or collection.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fdc0b8081909242fdc5cb1da517 |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.