Triple
T472716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astounding Award for Best New Writer |
E8593
|
entity |
| Predicate | typeOfWorkRecognized |
P1366
|
FINISHED |
| Object | prose fiction |
—
|
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: prose fiction | Statement: [Astounding Award for Best New Writer, typeOfWorkRecognized, prose fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWorkRecognized Context triple: [Astounding Award for Best New Writer, typeOfWorkRecognized, prose fiction]
-
A.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
B.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
C.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
D.
vocationType
Indicates the specific kind or category of occupation, profession, or calling associated with an entity.
-
E.
signatureWorkType
Indicates the specific category or type of work that serves as a defining or primary example associated with an entity.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff24108819092fdb85019ec4089 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.