Triple
T13594889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Fox |
E324790
|
entity |
| Predicate | cameoTypeInSequel |
P108137
|
FINISHED |
| Object | brief appearance |
—
|
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: brief appearance | Statement: [Bud Fox, cameoTypeInSequel, brief appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameoTypeInSequel Context triple: [Bud Fox, cameoTypeInSequel, brief appearance]
-
A.
cameoCharacter
chosen
Indicates that one entity appears briefly or in a minor, special-guest role within the context or work associated with another entity.
-
B.
hasSequelAppearance
Indicates that an entity appears again in a subsequent installment or sequel of a work.
-
C.
sequelAppearsIn
Indicates that a sequel (such as a follow-up work or installment) is featured, shown, or occurs within a specified context or medium.
-
D.
portrayedByInSequel
Indicates that an entity is portrayed by a particular actor or performer specifically in a sequel work (e.g., a sequel film, series, or game).
-
E.
hasDirectorCameo
Indicates that the director of a work appears in a cameo role within that same work.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.