Triple
T36152540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas |
E1045628
|
entity |
| Predicate | workFormatContext |
P84676
|
FINISHED |
| Object | illustrated book |
—
|
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: illustrated book | Statement: [Douglas, workFormatContext, illustrated book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workFormatContext Context triple: [Douglas, workFormatContext, illustrated book]
-
A.
basedInWorkFormat
Indicates that an entity operates or is situated within a particular work format (such as remote, hybrid, or on-site) as its primary mode of working.
-
B.
formatContext
chosen
Indicates the contextual or situational conditions under which a particular format is defined, applied, or interpreted.
-
C.
laborContext
Indicates the labor-related circumstances, conditions, or setting within which an action, relationship, or event takes place.
-
D.
workAttributedContext
Indicates that a work is associated with or derived from a particular contextual source, setting, or circumstance that informs its creation or interpretation.
-
E.
formOfWork
Indicates that one creative work is a specific form, version, or expression of another related work.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.