Triple
T18550848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip K. Dick Award |
E453371
|
entity |
| Predicate | fieldOfWorkOfNamesake |
P118673
|
FINISHED |
| Object | science fiction writing |
—
|
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: science fiction writing | Statement: [Philip K. Dick Award, fieldOfWorkOfNamesake, science fiction writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfWorkOfNamesake Context triple: [Philip K. Dick Award, fieldOfWorkOfNamesake, science fiction writing]
-
A.
eponymFieldOfWork
chosen
Indicates that a person is the namesake (eponym) of a particular field of work, discipline, or domain.
-
B.
namesakeOccupation
Indicates that one entity’s occupation is the same as, or derived from, the occupation associated with the other entity’s namesake.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
isNamedAfterOccupation
Indicates that an entity’s name is derived from or based on a particular occupation or profession.
-
E.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53800c0fc819097782f1e81574598 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.