Triple
T28780104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Heywood |
E726651
|
entity |
| Predicate | workStatusOfSource |
P174379
|
FINISHED |
| Object | unfinished 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: unfinished novel | Statement: [Charlotte Heywood, workStatusOfSource, unfinished novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStatusOfSource Context triple: [Charlotte Heywood, workStatusOfSource, unfinished novel]
-
A.
worksStatus
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
B.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
C.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
D.
hasWorkStatus
Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
-
E.
workKeyStatus
Indicates the current state or condition of a specific work key, such as whether it is active, valid, revoked, or otherwise in use.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 28, 2026, 6:19 a.m.