Triple
T37904825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Pocket Universe Empire |
E945517
|
entity |
| Predicate | hasPotentialGenre |
P167760
|
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: [Spanish Pocket Universe Empire, hasPotentialGenre, science fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPotentialGenre Context triple: [Spanish Pocket Universe Empire, hasPotentialGenre, science fiction]
-
A.
possibleGenre
chosen
Indicates that something may belong to, be classified under, or be associated with a particular genre as one of several potential genre options.
-
B.
hasGivenGenre
Indicates that an entity is associated with a specific genre that has been assigned or designated to it.
-
C.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
D.
hasNotableGenre
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
E.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 3, 2026, 4:20 p.m.