Triple
T23702296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father of the Pride |
E585626
|
entity |
| Predicate | includesUnairedEpisodes |
P152141
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Father of the Pride, includesUnairedEpisodes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesUnairedEpisodes Context triple: [Father of the Pride, includesUnairedEpisodes, true]
-
A.
includesPilotEpisode
Indicates that one entity (such as a series or collection) contains or features a pilot episode as part of its content.
-
B.
hasEpisodes
Indicates that one entity (typically a series or show) contains or is composed of multiple episode entities.
-
C.
unairedEpisodes
chosen
Indicates that there exist episodes of a show that have been produced but not yet broadcast or officially released.
-
D.
includesSpecialEpisodes
Indicates that the subject collection or series contains one or more special, non-regular episodes.
-
E.
hasMissingEpisode
Indicates that an entity (such as a series or season) is associated with one or more episodes that are absent or not available.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b683edb88190847d34640b6cfabe |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.