Triple
T37138849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dig |
E920047
|
entity |
| Predicate | originallyPlannedEpisodes |
P132279
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Dig, originallyPlannedEpisodes, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPlannedEpisodes Context triple: [Dig, originallyPlannedEpisodes, 13]
-
A.
originallyPlannedNumberOfEpisodes
chosen
Indicates the total number of episodes that were initially intended or planned for a series or program before any changes occurred.
-
B.
originallyPlannedSeasons
Indicates the number of seasons that were initially intended or scheduled for a series or show before any later changes or extensions.
-
C.
intendedEpisodes
Indicates that one entity is planned or designated to appear in, be used for, or be associated with specific episodes of another entity (such as a series or program).
-
D.
numberOfEpisodes
Indicates the total count of episodes associated with a given entity, such as a series or season.
-
E.
statusOfOriginalEpisodes
Indicates the current condition, availability, or release state of the original episodes in relation to a work or series.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.