Triple
T5246410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Writers’ Trust Fiction Prize |
E118469
|
entity |
| Predicate | typicalWorkFormat |
P32198
|
FINISHED |
| Object | novel |
—
|
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: novel | Statement: [Rogers Writers’ Trust Fiction Prize, typicalWorkFormat, novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWorkFormat Context triple: [Rogers Writers’ Trust Fiction Prize, typicalWorkFormat, novel]
-
A.
typicalReleaseFormat
chosen
Indicates the usual or standard format in which something is released or published.
-
B.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
typicalPictureFormat
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
E.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b5320748190bcf3be4b6c364f92 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.