Triple
T19454643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byers |
E486703
|
entity |
| Predicate | genreAssociationViaStrangerThings |
P38924
|
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: [Byers, genreAssociationViaStrangerThings, science fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreAssociationViaStrangerThings Context triple: [Byers, genreAssociationViaStrangerThings, science fiction]
-
A.
subjectOfFandom
Indicates that one entity is the focus or object of another entity’s fandom, admiration, or devoted interest.
-
B.
genreAssociatedWith
chosen
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
C.
genreRelation
Indicates a relationship where one entity is categorized as having, belonging to, or being associated with a particular genre defined by another entity.
-
D.
fandomClassification
Indicates how an entity is categorized or grouped within a particular fandom or fan community.
-
E.
fandomType
Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c117ac8190a38c01c3191beaea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.