Triple
T32868868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plebs |
E840735
|
entity |
| Predicate | specialEpisodeType |
P138291
|
FINISHED |
| Object | feature-length finale |
—
|
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: feature-length finale | Statement: [Plebs, specialEpisodeType, feature-length finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialEpisodeType Context triple: [Plebs, specialEpisodeType, feature-length finale]
-
A.
specialEpisodeAirDate
Indicates the calendar date on which a special episode is broadcast or made available to the public.
-
B.
notableEpisodeTypes
chosen
Indicates that certain types or categories of episodes are especially significant or noteworthy in relation to the subject.
-
C.
specialEdition
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
-
D.
specialBroadcasts
Indicates that one entity transmits or airs a broadcast that is designated as special or exceptional in some way to another entity or audience.
-
E.
specialFeature
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:17 a.m.