Triple
T37677101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Head |
E938124
|
entity |
| Predicate | hasGenreDescriptor |
P124610
|
FINISHED |
| Object | cult animated sci-fi series |
—
|
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: cult animated sci-fi series | Statement: [The Head, hasGenreDescriptor, cult animated sci-fi series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreDescriptor Context triple: [The Head, hasGenreDescriptor, cult animated sci-fi series]
-
A.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
B.
hasCanonicalGenre
Indicates that an entity is associated with its primary or officially recognized genre classification.
-
C.
hasGenreFunction
Indicates that something serves a particular genre-related role or function within a classification or organizational context.
-
D.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
-
E.
hasGenreRelation
chosen
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:18 p.m.