Triple
T28038663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-body |
E708477
|
entity |
| Predicate | hasGenreOfOrigin |
P179022
|
FINISHED |
| Object | science 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: science fiction | Statement: [P-body, hasGenreOfOrigin, science fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreOfOrigin Context triple: [P-body, hasGenreOfOrigin, science fiction]
-
A.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
-
B.
hasPrimaryGenreRegion
Indicates that an entity’s main or dominant genre is associated with a particular geographic region.
-
C.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
D.
hasOriginalGenre
Indicates that an entity was initially created or classified within a particular genre, before any later reclassification or adaptation.
-
E.
hasSourceMaterialGenre
Indicates that the genre of the source material from which something is derived is specified.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 27, 2026, 8:23 p.m.