Triple
T38629577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Way Down East |
E937412
|
entity |
| Predicate | basedOnWorkAdapter |
P200511
|
FINISHED |
| Object | Joseph R. Grismer |
—
|
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: Joseph R. Grismer | Statement: [Way Down East, basedOnWorkAdapter, Joseph R. Grismer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnWorkAdapter Context triple: [Way Down East, basedOnWorkAdapter, Joseph R. Grismer]
-
A.
basedOnWorkAdaptedTo
Indicates that one work is derived from and adapted based on the content, story, or elements of another pre-existing work.
-
B.
basedOnWorkComposer
Indicates that one work is derived from, adapted from, or otherwise created on the basis of another work by the specified composer.
-
C.
basedOnInWork
Indicates that one work is derived from, adapted from, or otherwise uses another work as its source or foundation.
-
D.
basedOnWorkAdaptations
Indicates that one work is an adaptation derived from, or created on the basis of, another pre-existing work.
-
E.
basedOnWorkCollection
Indicates that something is derived from, adapted from, or otherwise created using a particular collection of works as its source or foundation.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69ff90b5b98881909620033d78e4a9b8 |
completed | May 9, 2026, 7:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.