Triple
T16866014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | planet Mongo |
E410037
|
entity |
| Predicate | inspiredGenreWorks |
P62284
|
FINISHED |
| Object | later space opera settings |
—
|
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: later space opera settings | Statement: [planet Mongo, inspiredGenreWorks, later space opera settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredGenreWorks Context triple: [planet Mongo, inspiredGenreWorks, later space opera settings]
-
A.
inspiredWorksOf
chosen
Indicates that one entity served as the source of inspiration or creative influence for the works produced by another entity.
-
B.
genreOfProducedWorks
Indicates that one entity is the genre category to which the works produced by another entity belong.
-
C.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
D.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
E.
genreOfWorkContributedTo
Indicates that an entity contributed to a work belonging to a specified 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b5088f208190abfe937633ebe3fe |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.