Triple
T9836822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt (1929 film) |
E239121
|
entity |
| Predicate | filmProductionType |
P90244
|
FINISHED |
| Object | studio 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: studio film | Statement: [Thunderbolt (1929 film), filmProductionType, studio film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmProductionType Context triple: [Thunderbolt (1929 film), filmProductionType, studio film]
-
A.
filmType
Indicates the specific category or genre that a film belongs to.
-
B.
producedFilmType
Indicates that an entity (such as a person or organization) was responsible for producing a film of a specified type or category.
-
C.
filmTypeContext
Indicates the contextual relationship between a film and its type or category within a specific classification or usage setting.
-
D.
notableProductionType
Indicates that the subject is particularly known for producing or creating instances of the specified type.
-
E.
hasFictionalProductionType
Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
- F. None of above. chosen
Provenance (4 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb33b07688190b78a70cf535c3efc |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.