Triple
T10998068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creative Writing Fellowships |
E259933
|
entity |
| Predicate | outputExpected |
P96547
|
FINISHED |
| Object | new literary work |
—
|
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: new literary work | Statement: [Creative Writing Fellowships, outputExpected, new literary work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputExpected Context triple: [Creative Writing Fellowships, outputExpected, new literary work]
-
A.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
-
B.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
C.
outputDescription
Indicates that an entity produces or generates a particular description as its output.
-
D.
observedResult
Indicates that an entity has recorded or perceived a particular outcome, effect, or measurement resulting from some process or event.
-
E.
outputConfiguration
Indicates how the results or data produced by a process, system, or component are structured, formatted, or directed to their destination.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d20b448190958331705de3a9be |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.