Triple
T56321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo Award |
E1113
|
entity |
| Predicate | consideredOneOf |
P310
|
FINISHED |
| Object | major awards in speculative 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: major awards in speculative fiction | Statement: [Hugo Award, consideredOneOf, major awards in speculative fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredOneOf Context triple: [Hugo Award, consideredOneOf, major awards in speculative fiction]
-
A.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
B.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
C.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
D.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.