Triple
T6965089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Host (2013 film) |
E161467
|
entity |
| Predicate | hasSourceGenre |
P61875
|
FINISHED |
| Object | science fiction novel |
—
|
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 novel | Statement: [The Host (2013 film), hasSourceGenre, science fiction novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceGenre Context triple: [The Host (2013 film), hasSourceGenre, science fiction novel]
-
A.
hasSourceMaterialGenre
chosen
Indicates that the genre of the source material from which something is derived is specified.
-
B.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
-
C.
hasCanonicalGenre
Indicates that an entity is associated with its primary or officially recognized genre classification.
-
D.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
E.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1049e0819097099a0e9d15f787 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.