Triple
T13789495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilda Live |
E331355
|
entity |
| Predicate | featuresSaturdayNightLiveCharacters |
P93957
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gilda Live, featuresSaturdayNightLiveCharacters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSaturdayNightLiveCharacters Context triple: [Gilda Live, featuresSaturdayNightLiveCharacters, yes]
-
A.
franchiseCharacter
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
-
B.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
C.
musicalCharacter
Indicates that one entity is a character or role that appears within the other entity, which is a musical work or production.
-
D.
featuresCharacterWith
chosen
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
E.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de024af32c8190a9bd1278e09564ba |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.