Triple
T18293330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series I |
E438168
|
entity |
| Predicate | belongsToSeriesRange |
P131220
|
FINISHED |
| Object | I-series recommendations |
—
|
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: I-series recommendations | Statement: [Series I, belongsToSeriesRange, I-series recommendations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSeriesRange Context triple: [Series I, belongsToSeriesRange, I-series recommendations]
-
A.
belongsToSeriesEntry
Indicates that something is an individual installment or component within a larger series or sequence.
-
B.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
C.
belongsToSubseries
Indicates that one item is part of, or contained within, a more specific subseries of a larger series or collection.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
airedWithSeriesFrom
Indicates that one series was broadcast together or in conjunction with another series during its airing period.
- F. None of above. chosen
Provenance (4 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50100d6488190bbe73668df9c4046 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.