Triple
T12398849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells notice process |
E296193
|
entity |
| Predicate | responseMode |
P20198
|
FINISHED |
| Object | written Wells submission by recipient |
—
|
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: written Wells submission by recipient | Statement: [Wells notice process, responseMode, written Wells submission by recipient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseMode Context triple: [Wells notice process, responseMode, written Wells submission by recipient]
-
A.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
-
B.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
C.
responseExample
Indicates that one entity serves as an illustrative or sample response corresponding to another entity (such as a prompt, question, or situation).
-
D.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
-
E.
responseTool
chosen
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd448f08190af425a569d7ed158 |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed4cea08190ad374d3f6a798053 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.