Triple
T19547271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trem Carr Productions |
E489105
|
entity |
| Predicate | scaleOfOperation |
P10773
|
FINISHED |
| Object | Poverty Row-style production |
—
|
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: Poverty Row-style production | Statement: [Trem Carr Productions, scaleOfOperation, Poverty Row-style production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleOfOperation Context triple: [Trem Carr Productions, scaleOfOperation, Poverty Row-style production]
-
A.
operationScale
chosen
Indicates the relative size, scope, or magnitude at which an operation or activity is conducted.
-
B.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
C.
sectorOfOperation
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
D.
businessScale
Indicates the relative size or level of operations of a business, such as its scope, capacity, or market reach.
-
E.
hasLargeScale
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2d8a6081908e9bb3a6f5d85896 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.