Triple
T37602097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slim Hoover |
E935551
|
entity |
| Predicate | appearsInFilmType |
P97392
|
FINISHED |
| Object | feature film |
—
|
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 film | Statement: [Slim Hoover, appearsInFilmType, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInFilmType Context triple: [Slim Hoover, appearsInFilmType, feature film]
-
A.
filmAppearanceType
chosen
Indicates the type or nature of a subject’s appearance in a film, such as a role, cameo, or other participation category.
-
B.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
appearsInAdaptationBy
Indicates that an entity is featured or present in an adaptation created by a specified adapter (e.g., author, director, or studio).
-
D.
featuredInFilmGenre
Indicates that an entity (such as a film, character, or work) appears in or is associated with a specific film genre.
-
E.
featuredInFilmBy
Indicates that an entity is prominently included or showcased within a film that is created, directed, or produced by a specified person or organization.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:18 p.m.