Triple
T10418527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Lambert Strether |
E245582
|
entity |
| Predicate | taskInPlot |
P93485
|
FINISHED |
| Object | to bring Chad Newsome back to Woollett, Massachusetts |
—
|
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: to bring Chad Newsome back to Woollett, Massachusetts | Statement: [Lewis Lambert Strether, taskInPlot, to bring Chad Newsome back to Woollett, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskInPlot Context triple: [Lewis Lambert Strether, taskInPlot, to bring Chad Newsome back to Woollett, Massachusetts]
-
A.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
B.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
C.
taskName
Indicates the specific name or label assigned to a task within a process or workflow.
-
D.
taskForce
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
E.
notableWorkInPlot
Indicates that a work is prominently featured or plays a significant role within the plot of another work.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2938188190a908316d0a0959be |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:11 p.m.