Triple
T7917966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Venture Bros. |
E183874
|
entity |
| Predicate | seriesPremiereType |
P53894
|
FINISHED |
| Object | pilot episode |
—
|
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: pilot episode | Statement: [The Venture Bros., seriesPremiereType, pilot episode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesPremiereType Context triple: [The Venture Bros., seriesPremiereType, pilot episode]
-
A.
seriesPremiereOf
chosen
Indicates that one creative work (typically an episode) is the first-ever installment that begins a television or similar serialized series.
-
B.
sectionPremieredIn
Indicates that a specific section or part of a work first premiered or was initially presented in a particular event, venue, or context.
-
C.
seriesPremiereOnService
Indicates that a series has its first-ever episode or season debut made available on a particular service or platform.
-
D.
premieredOn
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
-
E.
premieredIn
Indicates that a creative work first publicly debuted or was initially presented in a particular place, event, or context.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.